Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advice for validating JMX exporter rules #972

Open
AagonP opened this issue Jun 8, 2024 · 1 comment
Open

Advice for validating JMX exporter rules #972

AagonP opened this issue Jun 8, 2024 · 1 comment
Assignees

Comments

@AagonP
Copy link

AagonP commented Jun 8, 2024

I have read through the documentation but I still encounter some challenges when working JMX exporter rules. So I'm opening this issue only to ask for advice on how we can better handle these scenarios when working with JMX exporter:

  1. When I was writing a rule like:
- pattern: "kafka.consumer<type=consumer-fetch-manager-metrics, client-id=(.+), topic=(.+), partition=(.+)><>records-lag"
      name: kafka_consumer_fetch_manager_records_lag

As I forget that JMX exporter rule regex is not anchored, kafka_consumer_fetch_manager_records_lag is actually presenting 3 metrics ( records-lag, records-lag-avg, records-lag-max). How can I avoid situation like this when certainly my goal was just to get the records-lag attribute.
2. Is there a way we can do linting for the configuration file?

Thanks for your time.

@dhoard
Copy link
Collaborator

dhoard commented Jun 12, 2024

Currently, there is no linter.

An out-of-band linting tool is hard to implement since the rules are based on the dynamically scraped MBeans.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants