Add a simple elastic search check #48
Merged
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
|
Sounds good to me! :) |
aphyr
added a commit
that referenced
this pull request
Jun 14, 2013
Add a simple elastic search check
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.
Adding a really simple elasticsearch health check. It parses the output from the
_cluster/healthwhich I think it semi-useful to get a quick idea about the cluster status.I'm also thinking of parsing the node stats that come from
_cluster/nodes/stats?all=truehowever I'm not sure if it's best to include that within the same tool, or make it a separate tool - perhaps with a toggle forall=true.What do you think?