Cherry-pick #10639 to 6.7: Fix missing nodes from Node Listing page when using Metricbeat Elasticsearch module with xpack.enabled: true #10672
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
…csearch module with xpack.enabled: true (elastic#10639) * Add source_node object to node_stats documents * Adding CHANGELOG entry (cherry picked from commit 6ddaae6)
cachedout
approved these changes
Feb 11, 2019
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.
Cherry-pick of PR #10639 to 6.7 branch. Original message:
Starting Metricbeat 6.6.0, if a user uses the
elasticsearchmodule for stack monitoring (by settingxpack.enabled: truein theirmodules.d/elasticsearch.yml), they will see no nodes in their Elasticsearch Node Listing page. 😮This is because the UI code relies on the
type=nodes_statsdocuments in.monitoring-es-*to contain asource_nodeproperty with certain fields in it. Theelasticsearch/node_statsmetricset wasn't indexing this property.This PR fixes this bug.