Clarify burst mode protection and non file based logging #8851
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.
Reading the docs my impression was that the reasons mentioned for burst mode protection do only apply to file-based logging or at least the examples only do.
Locking to the console is fairly common in cloud-based environments.
I have deactivated the burst mode protection (that had swallowed about 2/3s of our log messages) and the system is running fine without any impact on CPU or memory that I could spot.
So, this is part me wanting to clarify this in the doc but also part me checking in about my understanding of the interplay of this.
Thank you all so much for your work 💚