Trying to update participant attributes mid-call via PATCH /api/v2/conversations/{id}/participants. The request returns 200 OK, but the trace span in Jaeger drops. I’m injecting traceparent and W3C-TraceContext headers. The OTel SDK seems to ignore the context on this specific endpoint. Here’s the Python snippet using requests. Am I missing a header or is this a known SDK issue?
Trace headers don’t hop to Jaeger via that endpoint. You’ll need to push the context to your backend through participant attributes first, then extract it there for instrumentation.