-
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
Document privileges required for index lifecycle management #10421
Comments
I was able to successfully load the ILM policy, but ran into problems when I enabled ilm in the Metricbeat config. When I run Metricbeat with security enabled, but ILM disabled, Metricbeat ships events to Elasticsearch as expected. However, when I enable set
|
Here's the role I created for my testing (it didn't work):
Here's my output config:
|
I suspect that you may also need "view_index_metadata" in your indices privileges. We can confirm on our side too. |
@jakelandis Adding
I tried granting the |
Lee recommended these privileges via email:
|
I've labeled this as a blocker because without this users will find setting up beats correctly near impossible in 7.0 |
FWIW I've had luck with
I'm n ot an index rules expert though. |
Closed by #10449 |
I think I hit an issue with this today. It resulted in:
I fixed it by adjusting the index name to |
As a follow up to #9263, we need to document the privileges required to set up Beats to work with index life cycle management.
Note that the security docs indicate that
manage_ilm
is required, but the Kibana UI does not show the setting as available. I've been unable to get ILM working with security enabled and need additional input from dev.The text was updated successfully, but these errors were encountered: