- Legacy APM Server Reference:
- Overview
- Get started
- Set up
- How-to guides
- Configure
- Secure
- Monitor
- API
- Explore data in Elasticsearch
- Exported fields
- APM Application Metrics fields
- APM Error fields
- APM Profile fields
- APM Sourcemap fields
- APM Span fields
- APM Span Metrics fields
- APM Transaction fields
- APM Transaction Metrics fields
- APM Transaction Metrics fields
- Beat fields
- Cloud provider metadata fields
- Docker fields
- ECS fields
- Host fields
- Kubernetes fields
- Process fields
- System Metrics fields
- Troubleshoot
- Upgrade
- Release notes
- APM Server version 7.15
- APM Server version 7.14
- APM Server version 7.13
- APM Server version 7.12
- APM Server version 7.11
- APM Server version 7.10
- APM Server version 7.9
- APM Server version 7.8
- APM Server version 7.7
- APM Server version 7.6
- APM Server version 7.5
- APM Server version 7.4
- APM Server version 7.3
- APM Server version 7.2
- APM Server version 7.1
- APM Server version 7.0
- APM Server version 6.8
- APM Server version 6.7
- APM Server version 6.6
- APM Server version 6.5
- APM Server version 6.4
- APM Server version 6.3
- APM Server version 6.2
- APM Server version 6.1
- APM integration (Elastic Agent)
The Elastic APM integration became generally available in 7.16 — see the APM Guide for updated documentation. Standalone APM Server users can see the Legacy APM Overview and Legacy APM Server Reference.
Monitor APM Serveredit
You can use the Elastic Stack monitoring features to gain insight into the health of APM Server.
To monitor APM Server, make sure monitoring is enabled on your Elasticsearch cluster, then configure the method used to collect APM Server metrics. You can use one of following methods:
- Internal collection - Internal collectors send monitoring data directly to your monitoring cluster.
- Metricbeat collection - Metricbeat collects monitoring data from your APM Server instance and sends it directly to your monitoring cluster.
Was this helpful?
Thank you for your feedback.