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
fix(atenet): propagate trace context through router and namespace span/metric attrs
Fixes trace detachment in the router where two issues broke the trace chain:
1. Primary: resumer.go's singleflight used context.Background() inside
DoChan, so otelgrpc saw no parent span and ateapi handler spans
appeared in a separate trace. Now propagates the caller's span
context into the background context.
2. Secondary: the ext_proc HeadersResponse only rewrote :authority and
never injected traceparent/tracestate into the header mutation. Now
injects the trace context so the upstream worker receives the same
trace even when Envoy tracing is not configured.
3. Span and metric attributes used bare keys (atespace, actor, etc.)
instead of the ate.* convention established in #412. Renamed to
ate.atespace, ate.actor_name, ate.target_addr,
ate.actor_template_namespace, ate.actor_template_name, ate.outcome.
Fixes#427
0 commit comments