Batching Control

Backoff/Retry Settings

In situations where the destination tool is overloaded and/or returns HTTP 5xx or 4xx error codes, exponential backoff kicks in to prevent overloading the destination tool's API.

1. Max Batch Size: Maximum number of records to send in a single POST to the destination API
   1. Typically: 1000, but this depends on the destination’s ability to buffer the incoming data
2. Max Batch Delay: the maximum time to wait before building a batch and processing.
   1. Typically: 5 seconds
3. Base Retry Delay: The Initial delay time.  i.e for 2 seconds, the retries would proceed 2, 4, 8, 16, ... seconds later.
4. Max Intra-Retry Delay: Hard limit for the above retry delay. 
   1. For example: If set to 60 seconds, retries would be performed again  2, 4, 8, 16, 32, 32, 32... seconds later.
5. Max Retry Duration: Total time for retrying delivery.  For REST destinations, a delivery is a batch of events in one REST POST request.  
   1. For example: If set to 8 hours, then requests would be made based on the above settings for 2+4+8+16+32+32+32... until 8 hours in total duration is reached, then no subsequent attempts are made to retry sending the data.
   2. The assumption here is that if there is an outage or other issue with the destination tool, then recovery will take less than "Max Retry Duration" to complete.