- Legacy APM Server Reference:
- Overview
- Installing APM Server
- Upgrading APM Server
- Setting up and running APM Server
- Configuring APM Server
- General configuration options
- Configure the output
- Parse data by using ingest node
- Specify SSL settings
- Load the Elasticsearch index template
- Configure logging
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Set up Real User Monitoring (RUM) support
- Use environment variables in the configuration
- Set up project paths
- Securing APM Server
- Event Types
- Real User Monitoring (RUM)
- Tune Data Ingestion
- Storage Management
- Intake API
- Exploring data in Elasticsearch
- Exported fields
- Troubleshooting
- Release notes
A newer version is available. For the latest information, see the
current release documentation.
Overviewedit
The APM Server receives data from APM agents and transforms them into Elasticsearch documents.
It works by exposing an HTTP server to which agents post the APM data they collect.
APM Server is built with the Beats framework, and as such it leverages its functionality.
To get an overview of the whole Elastic APM system, also have a look at:
Was this helpful?
Thank you for your feedback.