This repository was archived by the owner on Feb 13, 2025. It is now read-only.
cmd/scollector: Fixed bug in ElasticSearch collector for Elastic 5.x #2155
Conversation
This file contains hidden or 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
Elastic 5.x route of `/_nodes/_local/stats` emits a single IP address, such as ``` "ip": "10.7.1.74:9300" ```` However prior to v5 this is an array: ``` "ip": [ "10.7.1.74:9300" ], ``` We do not use the IP address attribute from this route anywhere in the collector, so removing it from the JSON decoding stops the error, and has no impact on the collectors functionality (apart from making it work again).
captncraig
approved these changes
Aug 31, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Elastic 5.x route of
/_nodes/_local/statsemits a single IP address,such as
However prior to v5 this is an array:
We do not use the IP address attribute from this route anywhere in the
collector, so removing it from the JSON decoding stops the error, and has no
impact on the collectors functionality (apart from making it work again).