- 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
- Specify SSL settings
- Load the Elasticsearch index template
- Manual index lifecycle management
- Configure logging
- 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.
High Availabilityedit
To achieve high availability you can place multiple instances of APM Server behind a regular HTTP load balancer, for example HAProxy or nginx.
The endpoint /
always returns an HTTP 200
.
You can configure your load balancer to send HTTP requests to this endpoint
to determine if an APM Server is running.
See Server Information for more information on that endpoint.
In case of temporal issues, like unavailable Elasticsearch or a sudden high workload, the data is buffered in an internal memory queue and ingestion retried.
If a given APM Server process fails, the data that has not yet been forwarded to Elasticsearch is lost.
Was this helpful?
Thank you for your feedback.