A newer version is available. For the latest information, see the current release documentation.
« APM Server command reference APM Server and systemd »
Elastic Docs › ›Legacy APM Server Reference ›Set up APM Server

High Availability

edit

High Availability

edit

This method of installing APM Server will be deprecated and removed in a future release. Please consider getting started with the Elastic APM integration instead.

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.

« APM Server command reference APM Server and systemd »