This documentation refers to configuring the standalone (legacy) APM Server. This method of running APM Server will be deprecated and removed in a future release. Please consider upgrading to Fleet and the APM integration.
APM Server produces transaction histogram metrics that are used to power the APM app. Shifting this responsibility from APM app to APM Server removes the need to store unsampled transactions, reducing storage costs.
Example config file:
apm-server: aggregation: transactions: interval: 1m
Controls the frequency of metrics publication.
Maximum number of transaction groups to keep track of. Once exceeded, APM Server devolves into recording a metrics document for each transaction that is not in one of the transaction groups being tracked.
The fixed, worst-case percentage error (specified as a number of significant digits)
to maintain for recorded metrics.
Supported values are
See HDR histogram for more information.
Intro to Kibana
ELK for Logs & Metrics