Seeing a gap in our distributed tracing. The Web Messaging Guest API sends typing indicators via WebSocket, but the conversationId isn’t making it into the parent span context.
ws.send(JSON.stringify({ type: 'typing', conversationId: '123' }));
The backend receives it, but Jaeger shows no link to the upstream Data Action. How do we inject the trace context into the WebSocket frame payload so the span doesn’t break?