redpanda-data / redpanda-data/connect
Trace context not propagated in dynamic WebSocket input
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 969
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 64
Description
Hello,
We’re currently implementing distributed tracing in our system and ran into an issue with dynamic WebSocket input. We have an upstream service sending messages to redpanda-connect over dynamic websocket input. These messages already include trace context (traceparent / tracestate).
The problem here is when messages arrives via the dynamic websocket input:
- Benthos does not continue the existing trace context.
- Instead, it starts a new root trace.
As a result, we end up with two separate traces:
- One from the upstream service → until Benthos
- Another from Benthos → downstream services
These traces are not linked, breaking end-to-end observability.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the dynamic WebSocket input implementation and trace how incoming messages are handled. Inspect whether traceparent and tracestate are extracted before downstream processing, then verify the fix by confirming that messages retain the upstream trace rather than creating a separate root trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100