[STORM-4020] Why not Apache Storm gives an prometheus end point for metrics scraping?
- Dominant language
- Java
- Stars
- 6.7k
- Forks
- 4k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 62
Description
Why not Apache Storm gives an prometheus end point for metrics scraping for all the daemons or at-least for supervisor and nimbus?
The issue with reporter based mechanisms is that we have to create an external service (like push gateway) which can be a bottleneck.
Is there a best way, Apache Storm team suggests to scrape metrics to external systems like prometheus.
---
Originally reported by mharish12, imported from: Why not Apache Storm gives an prometheus end point for metrics scraping?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing how metrics are currently exposed through reporter-based mechanisms for the supervisor and nimbus daemons, and compare that with Prometheus scraping requirements. Done would mean a decided and documented approach for exposing daemon metrics to Prometheus without relying on an external push gateway.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, prometheus
- Domain
- distributed-systems, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100