stackabletech / stackabletech/hive-operator
Improve jmx exporter config for better metric output
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 29
- Forks
- 2
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 12
Description
We currently use a jmx exporter config without any rules (meaning the jmx exporter uses its basic schema to transform the jmx beans).
I did not find any preconfigured config files (like e.g. for zookeeper, kafka etc.). So we need to write the rules ourselves.
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
No file, test, or entry point is named. Start by locating the current JMX exporter configuration and reviewing the exporter's basic schema and existing metric output; done means the configuration contains appropriate rules and produces the intended metrics.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100