WebSocket reconnect drops OTel trace context

Trying to maintain distributed tracing across a WebSocket connection to wss://api.mypurecloud.com/api/v2/notification/events. The initial handshake includes the traceparent header, but the server’s acknowledgment doesn’t echo it back. Subsequent events arrive without any trace context. Is there a specific header or payload field I need to set in the subscription request to force context propagation? Here is the connection setup:

ws = create_connection(url, header=[f"traceparent: {ctx.get_traceparent()}"])

The trace breaks immediately after connection.

Terraform won’t fix runtime trace drops. Genesys WebSocket notifications don’t propagate OpenTelemetry headers. You’ll need to inject the trace context into the payload yourself on the client side. Check the event structure for custom attributes you can map to your tracing lib.