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
This consists of supporting two optional HTTP headers traceparent and tracestate on incoming requests, adopting the trace id from the traceparent header for internal traces and emitting updated or new headers on responses.
This will allow:
people using the gateway as a component in their infrastructure to correlate traces that pass through it
gateway providers to trace incoming requests and correlate with logs
performance optimizers to correlate traces with experiments
Of particular use will be the "sampled" flag on the emitted traceparent header that indicates whether the request was sampled for tracing by Kubo.
Checklist
Description
The HTTP gateway should support propagation of trace context headers using the W3C Trace Context recommendation.
This consists of supporting two optional HTTP headers
traceparent
andtracestate
on incoming requests, adopting the trace id from thetraceparent
header for internal traces and emitting updated or new headers on responses.This will allow:
Of particular use will be the "sampled" flag on the emitted
traceparent
header that indicates whether the request was sampled for tracing by Kubo.Implementation Note
This should be as simple as using the opentelemetry TraceContext, roughly:
The text was updated successfully, but these errors were encountered: