We’re trying to stitch together a distributed trace for call recordings using OpenTelemetry. The flow is simple: trigger a recording start via the REST API, then pass the recording ID to a Data Action that tags it with custom metadata for our Jaeger backend.
Here’s the weird part. The API call to start the recording returns 204 No Content as expected. But when I inject the traceparent header into that request, the span doesn’t show up in Jaeger. I’ve verified the SDK is injecting the headers correctly in the Python client.
POST /api/v2/recordings/conversations/interactions/{interactionId}
Headers:
Authorization: Bearer <token>
traceparent: 00-abc123def456...
The 204 response comes back instantly. No body. But the downstream Data Action, which waits for the recording.started webhook, sees a NULL trace context. Is the Genesys Cloud Recording API stripping custom headers before processing? Or am I missing a step to propagate context into the webhook event itself?
I’ve tried adding the trace ID to the attributes object in the Data Action input, but that feels like a hack. We need the automatic propagation to work.
{
"interactionId": "123-456",
"traceparent": "00-abc123..."
}
Does the Recording API support header passthrough for tracing? The docs are silent on this.