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 Oct 3, 2023. It is now read-only.
Using the latest version of the stackdriver exporter, traces that are exported don't respect the request's "X-Cloud-Trace-Context" header when determining the TraceID for the trace/span. This makes it not possible to correlate traces and logs in environments like AppEngine and Cloud Run, for which the load balancer sets the header before forwarding the request to the container.
Ideally, if a workaround can be provided in the meantime, that would be appreciated.
Using the latest version of the stackdriver exporter, traces that are exported don't respect the request's "X-Cloud-Trace-Context" header when determining the TraceID for the trace/span. This makes it not possible to correlate traces and logs in environments like AppEngine and Cloud Run, for which the load balancer sets the header before forwarding the request to the container.
Ideally, if a workaround can be provided in the meantime, that would be appreciated.