redpanda-data / redpanda-data/connect
Tracing - Adding span tags into processor/input/output spans based on message's attributes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 969
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 64
Description
Currently most of the spans created by our tracing system using opentelemetry will have 0 tags.
I think we should think a way to let users to manipulate the tags that will be generated by each span individually, in each processor/input/output. Currently we can only set tags that will be applied globally (to all spans).
I was thinking about a tracing_mapping for all benthos component to be able to generate tags based on any mapping applied to the message but I don't know if this would be the best approach.
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 by reviewing the tracing system and how spans are created for processors, inputs, and outputs. The issue does not name files, tests, or a settled mapping design; first determine how message attributes could be mapped to per-span tags and define completion criteria for component-level configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre, stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100