Add possibility to change prometheus metrics name
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
Hello,
Current [implementation](https://github.com/search?q=repo%3Alinkedin%2FBurrow%20burrow_kafka_consumer_&type=code) does not allow to change the `burrow_kafka_consumer_` prefix for Prometheus metrics. It would be convenient to configure these metrics names accordingly to the need. What do you think about it ?
This is especially problematic if you have multiple independent burrows with different configurations and one Prometheus storage.
Thank you in advance
Contributor guide
No contributing guide indexed for this repository
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 with the linked code search for the burrow_kafka_consumer_ prefix and trace how Prometheus metric names are assembled and configuration is loaded. Done means an independent Burrow can configure a different metric prefix and the emitted names use it consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100