Elasticsearch health check #109
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a health check for Elasticsearch.
The checker functions by making an HTTP request to the
/_cluster/healthendpoint and checking that thestatusfield included in the response isgreen.Should the Elasticsearch API return a non-200 HTTP status code or if the server's health status is anything other than
green, the health check will be marked as failed.In terms of SSL configuration, if a path to an SSL certificate is supplied in the configuration, the checker will use this certificate for the HTTPS request. Conversely, if no certificate is provided, the checker will proceed with the request using an insecure connection.