[exporter/sumologic] Modify retry settings to prevent exporter dropping data on transient backend unavailability.#47503
Merged
Conversation
Gourav2906
approved these changes
Apr 10, 2026
pankaj101A
approved these changes
Apr 10, 2026
crobert-1
approved these changes
Apr 10, 2026
andrzej-stencel
approved these changes
Apr 13, 2026
Co-authored-by: Curtis Robert <crobert@splunk.com> Co-authored-by: Andrzej Stencel <andrzej.stencel@elastic.co>
andrzej-stencel
added
the
ready to merge
AndrewCharlesHay
pushed a commit
to AndrewCharlesHay/opentelemetry-collector-contrib
that referenced
this pull request
Apr 23, 2026
…ng data on transient backend unavailability. (open-telemetry#47503) #### Description Modifying retry settings for sumologic exporter to be more reliable to transient backend unavailability. Currently data is dropped after 5 mins of retry, but we need a higher timeout limit. Increased total retry timeout from 5mins to 1hr. Added exponential backoff increasing from 5s to 5min. #### Testing 1. Unit tests passing 2. collector startup and exponential retry settings added verified with a dummy backend url which is unreachable. Sumologic exporter retry timeout started from 5s and grew exponentially. [testsumoExporter.log](https://github.com/user-attachments/files/26605794/testsumoExporter.log) --------- Co-authored-by: Andrzej Stencel <andrzej.stencel@elastic.co> Co-authored-by: Curtis Robert <crobert@splunk.com>
gracewehner
pushed a commit
to gracewehner/opentelemetry-collector-contrib
that referenced
this pull request
Apr 29, 2026
…ng data on transient backend unavailability. (open-telemetry#47503) #### Description Modifying retry settings for sumologic exporter to be more reliable to transient backend unavailability. Currently data is dropped after 5 mins of retry, but we need a higher timeout limit. Increased total retry timeout from 5mins to 1hr. Added exponential backoff increasing from 5s to 5min. #### Testing 1. Unit tests passing 2. collector startup and exponential retry settings added verified with a dummy backend url which is unreachable. Sumologic exporter retry timeout started from 5s and grew exponentially. [testsumoExporter.log](https://github.com/user-attachments/files/26605794/testsumoExporter.log) --------- Co-authored-by: Andrzej Stencel <andrzej.stencel@elastic.co> Co-authored-by: Curtis Robert <crobert@splunk.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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
Modifying retry settings for sumologic exporter to be more reliable to transient backend unavailability.
Currently data is dropped after 5 mins of retry, but we need a higher timeout limit.
Increased total retry timeout from 5mins to 1hr.
Added exponential backoff increasing from 5s to 5min.
Testing
testsumoExporter.log