Docs: Fix monitoring privileges #14307
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
dedemorton
approved these changes
Oct 30, 2019
9426270 to
44a91d9
Compare
|
With #14313 merged, |
jorgemarey
pushed a commit
to jorgemarey/beats
that referenced
this pull request
Jun 8, 2020
Adds `create_index` and `create_doc` on `.monitoring-beats-*` as required privileges to the monitoring role.
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.
I noticed that the monitoring role on https://www.elastic.co/guide/en/beats/filebeat/master/feature-roles.html#privileges-to-publish-monitoring only contains the
monitorcluster privilege. This is the lowest level cluster privilege that gives access to basic cluster APIs to retrieve things like cluster health and version, but does not allow writing data.This PR adds
create_indexandcreate_docon.monitoring-beats-*as required privileges to the monitoring role.