[AutoOps] Configure OTel Exporter to Send Maximum-sized Batches #10126
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
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.
elasticblr
approved these changes
Sep 24, 2025
SergioVerde
approved these changes
Sep 24, 2025
pickypg
added a commit
to elastic/autoops-install
that referenced
this pull request
Sep 24, 2025
Added configuration options for OTLP HTTP exporter so that batches are not rejected. This can be removed after 9.1.5 (after elastic/elastic-agent#10126 is exposed by default).
pickypg
added a commit
to elastic/autoops-install
that referenced
this pull request
Sep 24, 2025
Added configuration options for OTLP HTTP exporter so that batches are not rejected. This can be removed after 9.1.5 (after elastic/elastic-agent#10126 is exposed by default).
|
mergify bot
pushed a commit
that referenced
this pull request
Sep 24, 2025
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. (cherry picked from commit 476d721)
💚 Build Succeeded
History
cc @pickypg |
pickypg
added a commit
that referenced
this pull request
Sep 24, 2025
…) (#10133) 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. (cherry picked from commit 476d721) Co-authored-by: Chris Earle <[email protected]>
v1v
added a commit
that referenced
this pull request
Sep 26, 2025
* upstream: (505 commits) Update journald tests now that Filebeat supports watching folders (#10131) [deploy/kubernetes]: add info about hostPID for Universal Profiling (#10173) Fall back to process runtime if otel runtime is unsupported (#10087) Conditionall check for ms_tls13kdf build tag (#10160) [docs][edot] add entry for profiles (#10163) edot/docs: add support for profiles (#10146) Add Logstash exporter (#10137) Add back publish to serverless. (#10159) Improve Integration test documentation (#10155) Fix multiarch service image push from main to serverless (#10129) Forward migrate action to endpoint (#9801) Comment out check for ms_tls13kdf tag for FIPS-capable binaries (#10148) [otel] add receivers: apache, iis, mysql, postgresql, sqlserver v0.135.0 (#9344) Add k8sevents receiver in kube-stack (#10086) feat: emit system resource metrics for EDOT subprocess (#10003) [AutoOps] Configure OTel Exporter to Send Maximum-sized Batches (#10126) keep enrollment token when replacing data with signed (#10115) Revert "Publish `elastic-agent-service` container directly to serverless from main (#9583)" (#10127) Add agent_policy_id and policy_revision_idx to checkin requests (#9931) remove resource/k8s processor and use k8sattributes processor for service attributes (#10108) ...
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.
This configures the standard
sending_queueto batch-process and limit the maximum size of payloads being sent over the wire to avoid proxy and other rejections.Note:
max_sizeis uncompressed bytes andenableddefaults 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.