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
{{ message }}
This repository was archived by the owner on Feb 6, 2026. It is now read-only.
Context
In java-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.
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 googleapis/google-cloud-go#9302 to propagate correct TraceId and SpanId for logging and tracing correlation.
Client
java-logging
Context
In java-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.
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.
Design Docs:
OpenTelemetry Trace/Span ID Support in Cloud Logging Library
OpenTelemetry Trace/Span ID Support in Java Cloud Logging Library