Describe the bug
The Monitoring APM Server section in the docs describes how to configure the server to send monitoring data to Elasticsearch, and recommends using the built-in apm_system user/role.
In 7.2 this fails with an error in the logs like this:
Failed to publish events: 403 Forbidden: {"error":{"root_cause":[{"type":"security_exception","reason":"action [indices:data/write/bulk] is unauthorized for user [apm_system]"}],"type":"security_exception","reason":"action [indices:data/write/bulk] is unauthorized for user [apm_system]"},"status":403}
To Reproduce
Steps to reproduce the behavior:
- Create a 7.2 stack with security enabled. Set a password for the
apm_system user
- Configure apm-server.yml according to https://www.elastic.co/guide/en/apm/server/7.2/monitoring.html, using the password from step 1.
- Start the APM Server
- Check the logs, see there's an error
Expected behavior
Monitoring should work using the apm_system user/role.
Describe the bug
The Monitoring APM Server section in the docs describes how to configure the server to send monitoring data to Elasticsearch, and recommends using the built-in
apm_systemuser/role.In 7.2 this fails with an error in the logs like this:
To Reproduce
Steps to reproduce the behavior:
apm_systemuserExpected behavior
Monitoring should work using the apm_system user/role.