WARNING: Version 6.2 of APM Server has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Overview
editOverview
editWelcome to APM Server Docs.
The documentation pages are still work in progress. For more details also check APM Server Github repository.
APM Server is a central component in the Elastic APM system. It receives data from APM agents and transforms them into Elasticsearch documents.
To get an overview of the whole Elastic APM system, please also have a look at the documentation for
See how to Get Started with the Elastic APM system.
A single APM server can handle data from multiple services. APM Server works by exposing an HTTP server to which agents post the APM data they collect. This includes performance information about the services, as well as errors that occur in them.
APM Server is an application built in Go using the beats framework and as such it shares many of the same configuration options as beats.
In the following you can read more about