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

Add reason to elastic health check endpoint #42168

Closed
remmeier opened this issue May 16, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@remmeier
Copy link

commented May 16, 2019

In the Internet one can find countless questions about elastic having "yellow" and "red" health check status. It would be great to see this service providing the reason(s). Or maybe a second service that list the various performed checks with their individual health. This one may look similar to the Spring Boot Actuator health check service.

@polyfractal

This comment has been minimized.

Copy link
Member

commented May 16, 2019

Hi @remmeier. The health status is driven by the state of the shards in the cluster. E.g.

  • Green: all shards allocated
  • Yellow: all primaries allocated, one or more replicas missing
  • Red: One or more primaries missing

You can use the level flag to refine the status to see which index or shard is having problems. And the Cluster Allocation Explain will give more detailed information about why a particular shard is not allocating (no disk space, no free nodes based on filtering criteria, etc).

In the future, questions like this are best asked on the forums rather than Github. We try to reserve this repo for bug reports. Thanks! :)

@remmeier

This comment has been minimized.

Copy link
Author

commented May 16, 2019

yes that has cleared up how it works. The purpose of the ticket would have been to make it slightly more obvious to newbies like just me. So maybe add a second field given the health status in english words. Maybe follow HATEOAS and link the other cluster allocation endpoint, ... HATEOAS would in general be nice BTW to navigate the entire endpoint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.