Clarrify metricbeat must fetch data from all nodes #20441
Closed
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
This is a very important point, and is missing.
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
botelastic
bot
added
the
needs_team
❕ Build Aborted
Expand to view the summary
Build stats
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
andresrc
added
docs
Team:Services
|
Pinging @elastic/integrations-services (Team:Services) |
botelastic
bot
removed
the
needs_team
ycombinator
reviewed
Aug 10, 2020
| @@ -5,7 +5,7 @@ This file is generated! See scripts/mage/docs_collector.go | |||
| [[metricbeat-module-elasticsearch]] | |||
| == Elasticsearch module | |||
|
|
|||
| The `elasticsearch` module collects metrics about {es}. | |||
| The `elasticsearch` module collects metrics about {es}. In order to get all metricsets, you must install Metricbeat on each Elasticsearch node in the monitored cluster. | |||
There was a problem hiding this comment.
This is not quite true. Metricbeat could be installed anywhere and this module's hosts settings could be configured to point to all nodes in an Elasticsearch cluster.
Also, recently we introduced a scope: cluster setting that let's users point this module to any node in the Elasticsearch cluster: #18547.
|
Hi @ebuildy, thank you for your PR. We generally target PRs to |
|
Closing this PR because it's stalled, and it sounds like the content changes are not quite accurate. Please feel free to open a new PR if you want to submit other changes. (Tip: Change to the master branch in the docs before you click Edit.) |
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 is a very important point, and is missing.
What does this PR do?
Why is it important?
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs