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

How to monitor for Elasticsearch cluster status in phase "ApplyingChanges" using Prometheus? #8405

Open
johnswarbrick-napier opened this issue Jan 14, 2025 · 0 comments
Labels

Comments

@johnswarbrick-napier
Copy link

johnswarbrick-napier commented Jan 14, 2025

Hi -

When running Elasticsearch on Kubernetes, we occasionally see the Elasticsearch cluster status getting stuck in phase ApplyingChanges:

Image

The root cause of the Applying Changes status is due to #5979 with this error:

400 Bad Request: {Status:400 Error:{CausedBy:{Reason: Type:}
Reason:
Desired nodes with history [d7bf9e8e-47a0-40ad-8156-400ae519eb6c] and version [2] already exists with a different definition

We know how to workaround the issue by adding an annotation.

However I want to configure a Prometheus alert that fires whenever the Elasticsearch cluster is in status ApplyingChanges for more than 15 minutes.

The problem is that I cannot find any exported Prometheus metrics, for Elasticsearch, Elasticsearch Operator or Elasticsearch Exporter, which exposes the "phase" of ApplyingChanges

The cluster health metric indicates Green so isn't a reliable indicator of this failure state.

Does anyone know where I can get this ApplyingChanges status from in Prometheus?

Thanks.

@botelastic botelastic bot added the triage label Jan 14, 2025
@johnswarbrick-napier johnswarbrick-napier changed the title How to monitor for Elasticsearch cluster status in phase "Applying Changes" using Prometheus? How to monitor for Elasticsearch cluster status in phase "ApplyingChanges" using Prometheus? Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant