Recommend cluster scope for Metricbeat #70865
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
Today we mention Metricbeat's `scope` parameter but offer no guidance about how it should be used. This commit adds guidance to use `scope: cluster`, especially on clusters with dedicated master-eligible nodes.
DaveCTurner
added
>docs
elasticmachine
added
Team:Data Management
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-core-features (Team:Core/Features) |
thbkrkr
reviewed
Apr 7, 2021
Co-authored-by: thbkrkr <[email protected]>
|
@elasticmachine update branch |
|
merge conflict between base and head |
Comment on lines
49
to
51
| the cluster. If this is not possible, and the cluster does not use dedicated | ||
| master-eligible nodes, then install one {metricbeat} instance for each {es} | ||
| node in the production cluster and use the default `scope: node`. When |
There was a problem hiding this comment.
I find the and the cluster does not use dedicated master-eligible nodes a bit too hard/prescriptive. I would prefer to add a separate sentence that this is not recommended with dedicated master-eligible nodes and requires beefier master nodes than when using scope:cluster.
|
Thanks all! |
DaveCTurner
added a commit
that referenced
this pull request
May 10, 2021
Today we mention Metricbeat's `scope` parameter but offer no guidance about how it should be used. This commit adds guidance to use `scope: cluster`, especially on clusters with dedicated master-eligible nodes.
DaveCTurner
added a commit
that referenced
this pull request
May 10, 2021
Today we mention Metricbeat's `scope` parameter but offer no guidance about how it should be used. This commit adds guidance to use `scope: cluster`, especially on clusters with dedicated master-eligible nodes.
DaveCTurner
added a commit
that referenced
this pull request
May 10, 2021
Today we mention Metricbeat's `scope` parameter but offer no guidance about how it should be used. This commit adds guidance to use `scope: cluster`, especially on clusters with dedicated master-eligible nodes.
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.
Today we mention Metricbeat's
scopeparameter but offer no guidanceabout how it should be used. This commit adds guidance to use
scope: cluster, especially on clusters with dedicated master-eligible nodes.Closes #70853