- Legacy APM Server Reference:
- Overview
- Getting Started With APM Server
- Setting up APM Server
- Upgrading APM Server
- Configuring APM Server
- General configuration options
- Configure the output
- Parse data using ingest node pipelines
- SSL/TLS settings
- Load the Elasticsearch index template
- Index lifecycle management (ILM)
- Configure logging
- Configure the Kibana endpoint
- Set up Real User Monitoring (RUM) support
- Jaeger integration
- Use environment variables in the configuration
- Configure project paths
- Securing APM Server
- Monitoring APM Server
- Real User Monitoring (RUM)
- Tune Data Ingestion
- Storage Management
- API
- Exploring data in Elasticsearch
- Exported fields
- Troubleshooting
- Release notes
- APM Server version 7.6
- APM Server version 7.5
- APM Server version 7.4
- APM Server version 7.3
- APM Server version 7.2
- APM Server version 7.1
- APM Server version 7.0
- APM Server version 6.8
- APM Server version 6.7
- APM Server version 6.6
- APM Server version 6.5
- APM Server version 6.4
- APM Server version 6.3
- APM Server version 6.2
- APM Server version 6.1
Configure the outputedit
You configure APM Server to write to a specific output by setting options
in the Outputs section of the apm-server.yml
config file. Only a single
output may be defined.
The following topics describe how to configure each supported output. If you’ve secured the Elastic Stack, also read Securing APM Server for more about security-related configuration options.
Sourcemapsedit
Sourcemaps can be uploaded through all outputs but must eventually be stored in Elasticsearch.
When using outputs other than Elasticsearch, source_mapping.elasticsearch
must be set for source maps to be applied.
Be sure to update source_mapping.index_pattern
if sourcemaps are stored in the non-default location.
See source_mapping.elasticsearch
for more details.
fields
edit
Fields are optional tags that can be added to the documents that APM Server outputs.
They are defined at the top-level in your configuration file, and will apply to any configured output.
Fields can be scalar values, arrays, dictionaries, or any nested combination of these.
By default, the fields that you specify here will be grouped under a fields
sub-dictionary in the output document.
Example using the Elasticsearch output:
fields: {project: "myproject", instance-id: "574734885120952459"} #-------------------------- Elasticsearch output -------------------------- output.elasticsearch: hosts: ["localhost:9200"]
To store the custom fields as top-level fields, set the fields_under_root
option to true.
This is not recommended as when new fields are added to APM documents backward compatibility cannot be ensured.
On this page