Tracking the same issue as 9302 to propagate correct TraceId and SpanId for logging and tracing correlation.
Client
nodejs-logging
Context
In nodejs-logging libraries, the current implementation will always use a remote trace ID and span ID parsed from HTTP headers that originate from outside the application:
|
export function getOrInjectContext( |
As a result, logs are associated with the parent span rather than the span of interest.
Expected behavior
If the user is using opentelemetry instrumentation, we want to use the traceID and spanID of the span that OpenTelemetry created. This way, when a user looks for logs associated with that span, the logs produced by this logging library will appear.
Tracking the same issue as 9302 to propagate correct TraceId and SpanId for logging and tracing correlation.
Client
nodejs-logging
Context
In nodejs-logging libraries, the current implementation will always use a remote trace ID and span ID parsed from HTTP headers that originate from outside the application:
nodejs-logging/src/utils/context.ts
Line 95 in 53c5c24
As a result, logs are associated with the parent span rather than the span of interest.
Expected behavior
If the user is using opentelemetry instrumentation, we want to use the traceID and spanID of the span that OpenTelemetry created. This way, when a user looks for logs associated with that span, the logs produced by this logging library will appear.