[exporter/otlphttp] Add retryable_statuses to control which HTTP codes trigger retries #14260
+293
−30
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Author
|
Hi everyone, just checking in - is there anything needed from my side to help move this PR forward? Happy to make any adjustments. Thanks! |
Contributor
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
|
Not stale. |
evan-bradley
reviewed
Jan 9, 2026
…s trigger retries Fixes open-telemetry#14228
farhan-pasha
force-pushed
the
otlphttp-non-retryable-status
branch
from
a89de0f to
13e6247
Compare
farhan-pasha
changed the title
Author
|
@open-telemetry/collector-approvers friendly ping for feedback. Please let me know if I am missing something. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds a new
non_retryable_statusconfiguration field to the OTLP HTTP exporter'sretry_on_failuresection, allowing users to specify HTTP status codes that should NOT trigger internal retries.Problem: By default, the OTLP HTTP exporter retries on 429, 502, 503, and 504 per the OTLP specification. In gateway deployments, continuing to retry when backends return rate limits or temporary failures causes queue buildup and potential data loss.
Solution: This change allows treating normally-retryable codes as permanent errors, preventing internal retry loops.
Fixes #14228
Testing
Documentation