- Observability: other versions:
- Get started
- What is Elastic Observability?
- What’s new in 8.16
- Quickstart: Monitor hosts with Elastic Agent
- Quickstart: Monitor your Kubernetes cluster with Elastic Agent
- Quickstart: Monitor hosts with OpenTelemetry
- Quickstart: Unified Kubernetes Observability with Elastic Distributions of OpenTelemetry (EDOT)
- Quickstart: Collect data with AWS Firehose
- Add data from Splunk
- Applications and services
- Application performance monitoring (APM)
- Get started
- Learn about data types
- Collect application data
- View and analyze data
- Act on data
- Use APM securely
- Manage storage
- Configure APM Server
- Monitor APM Server
- APM APIs
- Troubleshooting
- Upgrade
- Release notes
- Known issues
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Multi-factor Authentication
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Scale and architect a deployment
- Synthetics support matrix
- Synthetics Encryption and Security
- Troubleshooting
- Real user monitoring
- Uptime monitoring (deprecated)
- Tutorial: Monitor a Java application
- Application performance monitoring (APM)
- CI/CD
- Cloud
- Infrastructure and hosts
- Logs
- Troubleshooting
- Incident management
- Data set quality
- Observability AI Assistant
- Reference
Enable APM Server binary debugging
editEnable APM Server binary debugging
editFleet-managed users should see View Elastic Agent logs to learn how to view logs and change the logging level of Elastic Agent.
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 publisher-related messages, start APM Server
with the publisher
selector:
apm-server -e -d "publisher"
If you want all the debugging output (fair warning, it’s quite a lot), you can
use *
, like this:
apm-server -e -d "*"