Add Fluent Bit retry configuration #12
Merged
Conversation
This file contains 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
By default Fluent Bit [uses](https://docs.fluentbit.io/manual/administration/scheduling-and-retries#configuring-retries) a Retry_Limit of 1. Since senders want to ensure that telemetry data is ingested, even if the observability backend (e.g. SAP Cloud Logging) is temporarily unavailable (e.g. due to network problems), we should recommend at least 3 retries.
|
Thanks Jannik. I’ve made the changes here: If this meets your approval I will push the changes out to PRODUCTION. |
|
Thanks! Approved from my side. |
|
I have pushed the changes out into PRODUCTION. We should see them after the next build, which usually happens on Thursday evenings. Please keep your eye out for the changes here: I'll be out of the office Thursday-Monday but I'll check when I get back on Tuesday August 27. |
keyes-bill
added
size/s
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
By default Fluent Bit uses a Retry_Limit of 1.
Since senders want to ensure that telemetry data is ingested, even if the observability backend (here SAP Cloud Logging) is temporarily unavailable (e.g. due to network problems), we should recommend at least 3 retries.