You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9Lines changed: 9 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -338,6 +338,15 @@ MIDDLEWARE = [
338
338
# ... other middlewares
339
339
]
340
340
```
341
+
342
+
You can configure the X-Ray recorder in a Django app under the ‘XRAY_RECORDER’ namespace. For a minimal configuration, the 'AWS_XRAY_TRACING_NAME' is required unless it is specified in an environment variable.
343
+
```
344
+
XRAY_RECORDER = {
345
+
'AWS_XRAY_TRACING_NAME': 'My application', # Required - the segment name for segments generated from incoming requests
346
+
}
347
+
```
348
+
For more information about configuring Django with X-Ray read more about it in the [API reference](https://docs.aws.amazon.com/xray-sdk-for-python/latest/reference/frameworks.html)
349
+
341
350
#### SQL tracing
342
351
If Django's ORM is patched - either using the `AUTO_INSTRUMENT = True` in your settings file
343
352
or explicitly calling `patch_db()` - the SQL query trace streaming can then be enabled or
0 commit comments