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 streams.
Elastic APM data is stored in data streams.
APM data follows the
<type>-<dataset>-<namespace> naming scheme.
dataset are predefined by the APM integration,
namespace is your opportunity to customize how different types of data are stored in Elasticsearch.
There is no recommendation for what to use as your namespace—it is intentionally flexible.
For example, you might create namespaces for each of your environments,
Or, you might create namespaces that correspond to strategic business units within your organization.
The namespace default is
To configure a custom namespace, set
apm-server: data_streams.namespace: custom_namespace
APM data streamsedit
By type, the APM data streams are:
Traces are comprised of spans and transactions. Traces are stored in the following data streams:
RUM and iOS agent application traces:
- Application traces:
Metrics include application-based metrics, aggregation metrics, and basic system metrics. Metrics are stored in the following data streams:
APM internal metrics:
- APM internal metrics:
Logs include application error events and application logs. Logs are stored in the following data streams:
APM error/exception logging:
- APM error/exception logging:
Sample APM documentsedit
Sample documents for each of the APM event types are available on these pages:
Elasticsearch query examplesedit
The following examples enable you to interact with Elasticsearch’s REST API. One possible way to do this is using Kibana’s Dev Tools console.
Data streams, templates, and index-level operations can also be manged via Kibana’s Index management panel.
To see an overview of existing data streams, run:
To query a specific event type, for example, application traces:
If you are interested in the settings and mappings of the Elastic APM indices, first, run a query to find template names:
Then, retrieve the specific template you are interested in:
Intro to Kibana
ELK for Logs & Metrics