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
@@ -57,6 +57,7 @@ Key | Type | Example | Description
57
57
**service** | str | "payment" | Service name defined. "service_undefined" will be used if unknown
58
58
**sampling_rate** | int | 0.1 | Debug logging sampling rate in percentage e.g. 10% in this case
59
59
**message** | any | "Collecting payment" | Log statement value. Unserializable JSON values will be casted to string
60
+
**xray_trace_id** | str | "1-5759e988-bd862e3fe1be46a994272793" | X-Ray Trace ID when Lambda function has enabled Tracing
60
61
61
62
## Capturing Lambda context info
62
63
@@ -304,7 +305,7 @@ This can be fixed by either ensuring both has the `service` value as `payment`,
304
305
305
306
You might want to continue to use the same date formatting style, or override `location` to display the `package.function_name:line_number` as you previously had.
306
307
307
-
Logger allows you to either change the format or suppress the following keys altogether at the initialization: `location`, `timestamp`, `level`, and `datefmt`
308
+
Logger allows you to either change the format or suppress the following keys altogether at the initialization: `location`, `timestamp`, `level`, `xray_trace_id`, and `datefmt`
Alternatively, you can also change the order of the following log record keys via the `log_record_order` parameter: `level`, location`, message`, and timestamp`
320
+
Alternatively, you can also change the order of the following log record keys via the `log_record_order` parameter: `level`, `location`, `message`, `xray_trace_id`, and `timestamp`
0 commit comments