- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.14
- Get started
- Observability AI Assistant
- Application performance monitoring (APM)
- Self manage APM Server
- Data Model
- Features
- Navigate the APM UI
- Perform common tasks in the APM UI
- Configure APM agents with central config
- Control access to APM data
- Create an alert
- Create and upload source maps (RUM)
- Create custom links
- Filter data
- Find transaction latency and failure correlations
- Identify deployment details for APM agents
- Integrate with machine learning
- Explore mobile sessions with Discover
- Observe Lambda functions
- Query your data
- Storage Explorer
- Track deployments with annotations
- OpenTelemetry integration
- Manage storage
- Configure
- Advanced setup
- Secure communication
- Monitor
- APM Server API
- APM UI API
- Troubleshoot
- Upgrade
- Release notes
- Known issues
- Log monitoring
- Infrastructure monitoring
- AWS monitoring
- Azure monitoring
- 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
- 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
- Uptime monitoring
- Real user monitoring
- Universal Profiling
- Alerting
- Service-level objectives (SLOs)
- Cases
- CI/CD observability
- Troubleshooting
- Fields reference
- Tutorials
Configure APM instrumentation
editConfigure APM instrumentation
edit
Instrumentation of APM Server is not yet supported for Fleet-managed APM.
APM Server uses the Elastic APM Go Agent to instrument its publishing pipeline. To gain insight into the performance of APM Server, you can enable this instrumentation and send trace data to APM Server. Currently, only the Elasticsearch output is instrumented.
Example configuration with instrumentation enabled:
instrumentation: enabled: true environment: production hosts: - "http://localhost:8200" api_key: L5ER6FEvjkmlfalBealQ3f3fLqf03fazfOV
Configuration options
editYou can specify the following options in the instrumentation section of the apm-server.yml config file:
enabled
editSet to true to enable instrumentation of APM Server.
Defaults to false.
environment
editSet the environment in which APM Server is running, for example, staging, production, dev, etc.
Environments can be filtered in the Kibana APM UI.
hosts
editThe APM Server hosts to report instrumentation data to.
Defaults to http://localhost:8200.
api_key
editAPI key used to secure communication with the APM Server(s).
If api_key is set then secret_token will be ignored.
secret_token
editSecret token used to secure communication with the APM Server(s).