-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fix missing nodes from Node Listing page when using Metricbeat Elasticsearch module with xpack.enabled: true #10639
Fix missing nodes from Node Listing page when using Metricbeat Elasticsearch module with xpack.enabled: true #10639
Conversation
Pinging @elastic/stack-monitoring |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we know which released versions this bug affected? |
jenkins, test this |
Looking at past branches, it appears that 6.6.0 was where this bug was introduced. |
@ycombinator K. I'm just thinking about what we might be able to do to raise awareness for people who run into this bug that it's a known issue and that it's since been fixed. Maybe it's worth at least filing a corresponding issue that people can search for? |
@cachedout I renamed this PR title to be more about the problem. That way if a user searches for any of those words, this PR should turn up in their results. |
jenkins, test this |
1 similar comment
jenkins, test this |
@ruflin I'd like you to review this, when you get a chance, please. Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did not test this on my end but code looks good.
…csearch module with xpack.enabled: true (elastic#10639) * Add source_node object to node_stats documents * Adding CHANGELOG entry (cherry picked from commit 6ddaae6)
…csearch module with xpack.enabled: true (elastic#10639) * Add source_node object to node_stats documents * Adding CHANGELOG entry (cherry picked from commit 6ddaae6)
…csearch module with xpack.enabled: true (elastic#10639) * Add source_node object to node_stats documents * Adding CHANGELOG entry (cherry picked from commit 6ddaae6)
…hen using Metricbeat Elasticsearch module with xpack.enabled: true (#10673) * Fix missing nodes from Node Listing page when using Metricbeat Elasticsearch module with xpack.enabled: true (#10639) * Add source_node object to node_stats documents * Adding CHANGELOG entry (cherry picked from commit 6ddaae6) * Removing extraneous changes
…csearch module with xpack.enabled: true (elastic#10639) * Add source_node object to node_stats documents * Adding CHANGELOG entry (cherry picked from commit 6ddaae6)
… page when using Metricbeat Elasticsearch module with xpack.enabled: true (elastic#10673) * Fix missing nodes from Node Listing page when using Metricbeat Elasticsearch module with xpack.enabled: true (elastic#10639) * Add source_node object to node_stats documents * Adding CHANGELOG entry (cherry picked from commit 9619718) * Removing extraneous changes
Starting Metricbeat 6.6.0, if a user uses the
elasticsearch
module for stack monitoring (by settingxpack.enabled: true
in 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_stats
documents in.monitoring-es-*
to contain asource_node
property with certain fields in it. Theelasticsearch/node_stats
metricset wasn't indexing this property.This PR fixes this bug.