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

Metric elasticsearch_cluster_health_up removed in v1.7.0 #847

Open
ncgee opened this issue Jan 8, 2024 · 0 comments
Open

Metric elasticsearch_cluster_health_up removed in v1.7.0 #847

ncgee opened this issue Jan 8, 2024 · 0 comments

Comments

@ncgee
Copy link

ncgee commented Jan 8, 2024

In version 1.7.0 metric elasticsearch_cluster_health_up was removed as "not useful" (per commit acddc580d6b807d3400a4d711cf2516049912f39). We have been using this metric as generic "exporter is up and able to collect (cluster health) data from Elasticsearch" metric to alert us when the exporter is unable to do so, using:

min without (endpoint, instance, service) (elasticsearch_cluster_health_up) == 0 or absent(elasticsearch_cluster_health_up)

We could use the up metric and check the absence of some other metric for this alert rule, but this provides no indication what kind of response the exporter receives from Elasticsearch. Can you elaborate on why elasticsearch_cluster_health_up was deemed not useful and suggest an alternative, or can the metric be reinstated?

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

No branches or pull requests

1 participant