This documentation refers to the standalone (legacy) method of running APM Server. This method of running APM Server will be deprecated and removed in a future release. Please consider upgrading to the Elastic APM integration. If you’ve already upgraded, see Data Model.
APM agents automatically pick up basic host-level metrics, including system and process-level CPU and memory metrics. Agent specific metrics are also available, like JVM metrics in the Java Agent, and Go runtime metrics in the Go Agent.
Infrastructure and application metrics are important sources of information when debugging production systems, which is why we’ve made it easy to filter metrics for specific hosts or containers in the Kibana metrics overview.
Metrics have the
processor.event property set to
Most agents limit keyword fields (e.g.
processor.event) to 1024 characters,
non-keyword fields (e.g.
system.memory.total) to 10,000 characters.
Metrics are stored in metric indices.
For a full list of tracked metrics, see the relevant agent documentation:
Intro to Kibana
ELK for Logs & Metrics