- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.13
- Get started
- Observability AI Assistant
- Application performance monitoring (APM)
- Self manage APM Server
- Data Model
- Features
- How-to guides
- OpenTelemetry integration
- Manage storage
- Configure
- Advanced setup
- Secure communication
- Monitor
- API
- Troubleshoot
- Upgrade
- Release notes
- Known issues
- Log monitoring
- Infrastructure monitoring
- AWS monitoring
- Azure monitoring
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Scale and architect a deployment
- Synthetics support matrix
- Synthetics Encryption and Security
- Troubleshooting
- Uptime monitoring
- Real user monitoring
- Universal Profiling
- Alerting
- Service-level objectives (SLOs)
- Cases
- CI/CD observability
- Troubleshooting
- Fields reference
- Tutorials
Grant privileges and roles needed for APM Agent central configuration
editGrant privileges and roles needed for APM Agent central configuration
editAPM Server agent central configuration management
editAPM Server acts as a proxy between your APM agents and the APM app. The APM app communicates any changed settings to APM Server so that your agents only need to poll the Server to determine which central configuration settings have changed.
To grant an APM Server user with the required privileges for managing central configuration in Elasticsearch without Kibana, assign the user the following privileges:
| Type | Privilege | Purpose |
|---|---|---|
Index |
|
Allow APM Server to manage central configurations in Elasticsearch |
The above privileges should be sufficient for APM agent central configuration to work properly as long as APM Server communicates with Elasticsearch successfully. If it fails, it may fallback to read agent central configuration via Kibana if configured, which requires the following privileges:
| Type | Privilege | Purpose |
|---|---|---|
Spaces |
|
Allow APM Server to manage central configurations via the APM app |
Looking for privileges and roles needed to use central configuration from the APM app or APM app API? See APM app central configuration user.