Improve jmx exporter config for better metric output

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
observability

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.

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.

Dominant language
Rust
Stars
29
Forks
2
Avg merge
1d 19h
Merged PRs (30d)
12

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/hive-operator

All issues in stackabletech/hive-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.