Tune data ingestion

This section explains how to adapt data ingestion according to your needs.

If the APM Server cannot process data quickly enough, you will see request timeouts. One way to solve this problem is to increase processing power.

Increase processing power by either migrating to a more powerful machine or adding more APM Server/Elastic Agent instances. Having several instances will also increase availability.

Large payloads may result in request timeouts. You can reduce the payload size by decreasing the flush interval in the agents. This will cause agents to send smaller and more frequent requests.

Optionally you can also reduce the sample rate or reduce the amount of stack traces.

Read more in the agents documentation.

Agents make use of long running requests and flush as many events over a single request as possible. Thus, the rate limiter for anonymous authentication is bound to the number of events sent per second, per IP.

If the event rate limit is hit while events on an established request are sent, the request is not immediately terminated. The intake of events is only throttled to anonymous event rate limit, which means that events are queued and processed slower. Only when the allowed buffer queue is also full, does the request get terminated with a 429 - rate limit exceeded HTTP response. If an agent tries to establish a new request, but the rate limit is already hit, a 429 will be sent immediately.

Increasing the default value for the following configuration variable will help avoid rate limit exceeded errors:

The Elasticsearch Reference provides insight on tuning Elasticsearch.

Tune for indexing speed provides information on:

Tune for disk usage provides information on: