Snowbridge retry behavior configuration (beta)
This feature was added in version 3.0.0
This feature is in beta status because we may make breaking changes in future versions.
This feature allows you to configure the retry behavior when the target encounters a failure in sending the data. There are three types of failure you can define:
A transient failure is a failure which we expect to succeed again on retry. For example, some temporary network error. Typically, you would configure a short backoff for this type of failure. When we encounter a transient failure, we keep processing the rest of the data as normal, under the expectation that everything is operating as normal. The failed data is retried after a backoff.
A setup failure is one we don't expect to be immediately resolved, for example an incorrect address, or an invalid API key. Typically, you would configure a long backoff for this type of failure, under the assumption that the issue needs to be fixed with either a configuration change or a change to the target itself (e.g. permissions need to be granted). Setup errors will be retried up to the configured max_attempts before the app crashes.
A throttle failure (added in version 4.0.0) is a special type of failure that indicates the target is rate limiting requests. This is handled separately from transient errors to allow different retry behavior - typically with longer delays to respect rate limits.
As of version 3.0.0, only the http target can be configured to return setup and throttle errors, via response rules - see the http target configuration section. For all other targets, all errors returned will be considered transient, and behavior can be configured using the transient block of the retry configuration.
Retries will be attempted with an exponential backoff. In other words, on each subsequent failure, the backoff time will double. You can configure transient failures to be retried indefinitely by setting max_attempts to 0.
As of version 4.0.0, you can configure transient failures to be sent to the failure target after reaching max_attempts by setting invalid_after_max to true.
Configuration options
loading...