Missing "stream" metric label in Streams Mode
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- observability
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.
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
...
- Dominant language
- Go
- Stars
- 571
- Forks
- 121
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 15
Getting set up
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.
More from redpanda-data/benthos
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
redpanda-data/benthos#404 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
redpanda-data/benthos#503 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
redpanda-data/benthos#502 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 72/100
redpanda-data/benthos#481 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
redpanda-data/benthos#469 ·
Maintainers usually reply within 1 day
All issues in redpanda-data/benthos
Similar issues
-
Remove CAAPFOpenkind/chore kind/cleanup needs-area
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
rancher/turtles#2848 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
priority: low 🌱 type: enhancement 💅🏼
Difficulty 2/5 Half a day Newbie friendliness 84/100
nebari-dev/llm-serving-pack#199 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kedacore/keda#8225 · 1 comment ·
Maintainers usually reply within 1 day