[AutoOps] Improve Batching Configuration#10492
Merged
Conversation
This brings in recommendations from external testing on OTel data shipping to better understand solid batching. Note: `block_on_overflow: true` is going to become the default behavior in a future version of OTel.
pickypg
added
bug
Contributor
|
@pickypg are we going to also update the https://github.com/elastic/elastic-agent/blob/main/deploy/helm/edot-collector/kube-stack/values.yaml? If yes, in this are we going to split the otlphttp exporter one for logs and one for metrics/traces? |
Member
Author
This PR is explicitly for AutoOps for Self-managed (via Cloud Connected) usage, which currently only uses the There is a wider effort that is standardizing the batching behavior for EDOT, but it's not intended to be this PR. |
Contributor
💚 Build Succeeded
History
cc @pickypg |
mergify bot
pushed a commit
that referenced
this pull request
Oct 14, 2025
This brings in recommendations from external testing on OTel data shipping to better understand solid batching. Note: `block_on_overflow: true` is going to become the default behavior in a future version of OTel. (cherry picked from commit 552463b)
8 tasks
mergify bot
pushed a commit
that referenced
this pull request
Oct 14, 2025
This brings in recommendations from external testing on OTel data shipping to better understand solid batching. Note: `block_on_overflow: true` is going to become the default behavior in a future version of OTel. (cherry picked from commit 552463b)
8 tasks
pickypg
added a commit
that referenced
this pull request
Oct 14, 2025
This brings in recommendations from external testing on OTel data shipping to better understand solid batching. Note: `block_on_overflow: true` is going to become the default behavior in a future version of OTel. (cherry picked from commit 552463b) Co-authored-by: Chris Earle <pickypg@users.noreply.github.com>
pickypg
added a commit
that referenced
this pull request
Oct 14, 2025
This brings in recommendations from external testing on OTel data shipping to better understand solid batching. Note: `block_on_overflow: true` is going to become the default behavior in a future version of OTel. (cherry picked from commit 552463b) Co-authored-by: Chris Earle <pickypg@users.noreply.github.com>
hayotbisonai
pushed a commit
to hayotbisonai/elastic-agent
that referenced
this pull request
Nov 23, 2025
This brings in recommendations from external testing on OTel data shipping to better understand solid batching. Note: `block_on_overflow: true` is going to become the default behavior in a future version of OTel.
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
4 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.
This brings in recommendations from external testing on OTel data shipping to better understand solid batching.
Note:
block_on_overflow: trueis going to become the default behavior in a future version of OTel.What does this PR do?
Updates the batching behavior of the OTLP exporter to be more performant.
Why is it important?
This should improve performance end-to-end.
Checklist
I have made corresponding changes to the documentationI have added tests that prove my fix is effective or that my feature works./changelog/fragmentsusing the changelog toolI have added an integration test or an E2E testDisruptive User Impact
None. This should actually improve performance in practically all scenarios.
How to test this PR locally
Run the Elastic Agent using the configurations provided and ensure it still ships data.
Related issues
Internal discussions around better queueing.