[9.1] (backport #10126) [AutoOps] Configure OTel Exporter to Send Maximum-sized Batches #10133
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.
This configures the standard
sending_queue
to batch-process and limit the maximum size of payloads being sent over the wire to avoid proxy and other rejections.Note:
max_size
is uncompressed bytes andenabled
defaults totrue
, but it's unused if no settings are set. I want to ensure a future release doesn't flip the default tofalse
.What does this PR do?
It limits the size of requests being sent over the wire to a more reasonable size.
Why is it important?
Sending large payloads can trigger security issues as well as rejections at many levels.
This is an automatic backport of pull request #10126 done by [Mergify](https://mergify.com).