- Legacy APM Server Reference:
- Overview
- Get started
- Set up
- How-to guides
- Configure
- Secure
- Monitor
- API
- Explore data in Elasticsearch
- Exported fields
- Troubleshoot
- Release notes
- APM Server version 7.7
- 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
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.