- Legacy APM Server Reference:
- Overview
- Installing APM Server
- Upgrading APM Server
- Setting up and running APM Server
- Configuring APM Server
- General configuration options
- Configure the output
- Parse data using ingest node pipelines
- Specify SSL settings
- Load the Elasticsearch index template
- Configure logging
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Set up Real User Monitoring (RUM) support
- Use environment variables in the configuration
- Set up project paths
- Securing APM Server
- Monitoring APM Server
- Real User Monitoring (RUM)
- Tune Data Ingestion
- Storage Management
- Intake API
- Exploring data in Elasticsearch
- Exported fields
- Troubleshooting
- Release notes
A newer version is available. For the latest information, see the
current release documentation.
Debugedit
By default, APM Server sends all its output to syslog. When you run APM Server in
the foreground, you can use the -e
command line flag to redirect the output to
standard error instead. For example:
apm-server -e
The default configuration file is apm-server.yml (the location of the file varies by
platform). You can use a different configuration file by specifying the -c
flag. For example:
apm-server -e -c myapm-serverconfig.yml
You can increase the verbosity of debug messages by enabling one or more debug
selectors. For example, to view the published transactions, you can start APM Server
with the publish
selector like this:
apm-server -e -d "publish"
If you want all the debugging output (fair warning, it’s quite a lot), you can
use *
, like this:
apm-server -e -d "*"
Was this helpful?
Thank you for your feedback.