redpanda-data / redpanda-data/benthos
Missing "stream" metric label in Streams Mode
Open
Nobody has claimed this yet.
needs investigation
observability
- Dominant language
- Go
- Stars
- 571
- Forks
- 120
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 18
Description
In Streams Mode, the stream label is missing from processor_resources. Without this label, differentiating metrics across multiple streams becomes impossible.
It would be greatly appreciated to have entries for the pipeline processors of type resource, which currently do not emit any metrics. This would certainly serve as a workaround.
processor_received{instance="worker-2", path="root.pipeline.processors.0", stream="abc"} 21
processor_received{instance="worker-2", path="root.pipeline.processors.15", stream="abc"} 0
processor_received{instance="worker-2", path="root.pipeline.processors.16", stream="abc"} 0
...
processor_received{instance="worker-2", path="root.processor_resources.branch.processors.0"} 21
processor_received{instance="worker-2", path="root.processor_resources.branch.processors.0.try.0"} 21
processor_received{instance="worker-2", path="root.processor_resources.branch.processors.0.try.1"} 18
...
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 tracing the Streams Mode metrics path for processor_resources and compare it with the processor metrics shown in the issue. Done means processor_resources metrics include the stream label and resource-type pipeline processors emit the expected processor metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100