- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.14
- Get started
- Observability AI Assistant
- Application performance monitoring (APM)
- Self manage APM Server
- Data Model
- Features
- Navigate the APM UI
- Perform common tasks in the APM UI
- Configure APM agents with central config
- Control access to APM data
- Create an alert
- Create and upload source maps (RUM)
- Create custom links
- Filter data
- Find transaction latency and failure correlations
- Identify deployment details for APM agents
- Integrate with machine learning
- Explore mobile sessions with Discover
- Observe Lambda functions
- Query your data
- Storage Explorer
- Track deployments with annotations
- OpenTelemetry integration
- Manage storage
- Configure
- Advanced setup
- Secure communication
- Monitor
- APM Server API
- APM UI 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
Configure APM agent configuration
editConfigure APM agent configuration
editAPM agent configuration allows you to fine-tune your APM agents from within the APM UI. Changes are automatically propagated to your APM agents, so there’s no need to redeploy your applications.
To learn more about this feature, see APM agent configuration.
Here’s a sample configuration:
apm-server.agent.config.cache.expiration: 45s apm-server.agent.config.elasticsearch.api_key: TiNAGG4BaaMdaH1tRfuU:KnR6yE41RrSowb0kQ0HWoA
APM agent configuration options
editThe following options are only supported for APM Server binary users.
You can specify these options in the apm-server.agent.config
section of the
apm-server.yml
config file:
apm-server.agent.config.cache.expiration
editWhen using APM agent configuration, information fetched from Elasticsearch will be cached in memory for some time.
Specify the cache expiration time via this setting. Defaults to 30s
(30 seconds).
apm-server.agent.config.elasticsearch
editTakes the same options as output.elasticsearch.
For APM Server binary users and Elastic Agent standalone-managed APM Server,
APM agent configuration is automatically fetched from Elasticsearch using the output.elasticsearch
configuration. If output.elasticsearch
isn’t set or doesn’t have sufficient privileges,
use these Elasticsearch options to provide Elasticsearch access.
Common problems
editYou may see either of the following HTTP 403 errors from APM Server when it attempts to fetch APM agent configuration:
APM agent log:
"Your Elasticsearch configuration does not support agent config queries. Check your configurations at `output.elasticsearch` or `apm-server.agent.config.elasticsearch`."
APM Server log:
rejecting fetch request: no valid elasticsearch config
This occurs because the user or API key set in either apm-server.agent.config.elasticsearch
or output.elasticsearch
(if apm-server.agent.config.elasticsearch
is not set) does not have adequate permissions to read source maps from Elasticsearch.
To fix this error, ensure that APM Server has all the required privileges. See Use feature roles for more details.
On this page