Ignite JMX metrics seems to have huge number of Unique Values for Attributes. This causes slower metrics scraping on prometheus. [See attached Screenshot]
Open
- Dominant language
- Java
- Stars
- 5.1k
- Forks
- 1.9k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
**Steps to Reproduce issue:**
1. Start ignite and expose metrics via JMX.
2. Setup Prometheus jmx exporter to export these ignite metrics on Prometheus.
3. Configure Prometheus to scrape ignite metrics from Prometheus jmx exporter.
Contributor guide
Research direction
Reproduce the issue by starting Ignite, exposing metrics through JMX, configuring the Prometheus JMX exporter, and scraping them with Prometheus. Compare the exported attribute cardinality and scrape performance; the issue needs a defined metric change and a reproducible validation of reduced unique values and slower scraping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, prometheus
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100