Skip to content

Batching Configuration Standardization Project#3477

Merged
mx-psi merged 11 commits into
open-telemetry:mainfrom
braydonk:batching_project
Jun 10, 2026
Merged

Batching Configuration Standardization Project#3477
mx-psi merged 11 commits into
open-telemetry:mainfrom
braydonk:batching_project

Conversation

@braydonk

@braydonk braydonk commented May 27, 2026

Copy link
Copy Markdown
Contributor

This PR is to launch an official project to standardize configuration for batching across the OpenTelemetry ecosystem. The background and justification for this project are documented within. This is a short-term project with definitive deliverables and a (relatively) definitive end, and as such isn't currently using "SIG" verbiage.

This project has already organized a TC sponsor (@jmacd) and a GC liaison (@mx-psi), as well as some of the designers/implementing engineers we will need (@XuechunHou @iblancasa). We are still looking for more voices to round out the designing group, and more implementing engineers for other languages.

As of writing, it isn't officially decided whether we will put a recurring sync on the OpenTelemetry Community Calendar or work async with ad-hoc synchronous meetings as needed.

This PR is to launch an official project to standardize configuration
for batching across the OpenTelemetry ecosystem. The background and
justification for this project are documented within.

This project has already organized a TC sponsor and GC liaison, as well
as some implementing engineers. We are still looking for more voices to
round out the designing group and implementing engineers for other
languages.

As of writing this description, we still need to coordinate a time on
the OpenTelemetry calendar. It isn't officially decided whether we will
put a recurring sync on the calendar or work async with ad-hoc
synchronous meetings as needed.
Comment thread projects/batching-config-standardization.md
Comment thread projects/batching-config-standardization.md Outdated
Comment thread projects/batching-config-standardization.md Outdated
Comment thread projects/batching-config-standardization.md Outdated
Comment thread projects/batching-config-standardization.md Outdated
Comment thread projects/batching-config-standardization.md Outdated
Comment thread projects/batching-config-standardization.md Outdated
Comment thread projects/batching-config-standardization.md Outdated
Comment thread projects/batching-config-standardization.md Outdated
Comment thread projects/batching-config-standardization.md
Comment thread projects/batching-config-standardization.md Outdated
Comment thread projects/batching-config-standardization.md Outdated

@cijothomas cijothomas left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Left some minor comments, nothing blockers.
(Only thing which I'd remove is the OpenTelemetry GA phrasing, as it is an undefined term, and removing it won't hurt this proposal in any way)

Thanks for organizing this!

Comment thread projects/batching-config-standardization.md
@braydonk

braydonk commented Jun 2, 2026

Copy link
Copy Markdown
Contributor Author

That CI failure looks like a GitHub 0 9's of availability moment

@reyang reyang added triage:accepted This issue has been accepted and will be worked. and removed triage:tc-inbox labels Jun 3, 2026
@github-project-automation github-project-automation Bot moved this to Todo in GC Work Jun 3, 2026
@reyang reyang added triage:tc-reviewed TC has reviewed this proposal and offered initial feedback/direction and removed triage:accepted This issue has been accepted and will be worked. labels Jun 3, 2026
@reyang

reyang commented Jun 3, 2026

Copy link
Copy Markdown
Member

The TC has discussed about this and we're supportive.

@jmacd

jmacd commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

@braydonk I think the next step ideally will be to present a document for a wide audience to review with the various proposals that have been made and the analysis, ideally recommending a consensus opinion reached by you, @mx-psi @XuechunHou, @iblancasa and others. Thank you!

@braydonk

braydonk commented Jun 4, 2026

Copy link
Copy Markdown
Contributor Author

Thanks everyone!

I think the next step ideally will be to present a document for a wide audience to review with the various proposals that have been made and the analysis

I will begin work on that ASAP. Since the project seems well supported enough, I opened up the #otel-batching-standardization Slack channel in the CNCF Slack Channel to organize initial collaboration.

I will plan to have something presentable by the next Specification SIG call.

@mx-psi
mx-psi added this pull request to the merge queue Jun 10, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 10, 2026
@mx-psi
mx-psi enabled auto-merge June 10, 2026 10:25
@mx-psi
mx-psi added this pull request to the merge queue Jun 10, 2026
Merged via the queue into open-telemetry:main with commit 9180905 Jun 10, 2026
8 of 10 checks passed
@github-project-automation github-project-automation Bot moved this from Todo to Done in GC Work Jun 10, 2026
@braydonk

Copy link
Copy Markdown
Contributor Author

Thank you for the merge! Very exciting!

I will plan to have something presentable by the next Specification SIG call.

Evidently I did not get something presentable by the next Specification SIG call. 🙂

I am working on that as well as getting started on other organization tasks such as the project board. If you want to follow any further updates to this project, please check out the #otel-batching-standardization CNCF Slack Channel. Thanks everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage:tc-reviewed TC has reviewed this proposal and offered initial feedback/direction

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.