-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Component/s: Observability
-
Needed
Amend the OpenTelemetry and Logging specifications so that, when tracing is enabled, driver log messages can be correlated with the active trace.
- Scope rule (MUST, all drivers): command, server selection and connection checkout/check-in log messages are emitted while their covering span (command span or operation span) is the current span, in sync and async paths.
- Fields rule (SHOULD, drivers with driver-managed log output only, e.g. C, Go, Node): add trace_id, span_id, trace_flags (OpenTelemetry non-OTLP log names) to those messages. Drivers logging through an application-configured framework (SLF4J, ILogger, Python logging, Rust tracing) MUST NOT add them.
- related to
-
DRIVERS-719 Client Side Support for OpenTelemetry
-
- In Progress
-
-
JAVA-5734 Context Propagation in Logs
-
- In Progress
-