Repository navigation
Add OTEL_METRIC_EXPORT_MAX_BATCH_SIZE env var for Periodic exporting MetricReader - #5359
Merged
Merged
Conversation
Pull request dashboard statusMerged · refreshed 2026-10-27 19:05 UTC Status above doesn't look right?
|
psx95
force-pushed
the
max-export-batch-size-env
branch
from
October 14, 2026 19:02
451370c to
9b947ac
Compare
psx95
marked this pull request as ready for review
October 14, 2026 19:35
dashpole
approved these changes
Oct 14, 2026
dashpole
left a comment
dashpole
left a comment
Contributor
There was a problem hiding this comment.
I'm generally against adding new environment variables now that declarative configuration is stable, but I am supportive of adding this one:
- It satisfies the requirements of the (now ancient) environment variable moratorium (statically typed, primitive integer).
- It is nice for consistency, since all the other
Periodic exporting MetricReaderoptions (OTEL_METRIC_EXPORT_INTERVAL,OTEL_METRIC_EXPORT_TIMEOUT) and the equivalent batch size knobs in Traces (OTEL_BSP_MAX_EXPORT_BATCH_SIZE) and Logs (OTEL_BLRP_MAX_EXPORT_BATCH_SIZE) are available as environment variables. - Both @cijothomas and @jack-berg have previously expressed some openness to having a spec-level environment variable for this.
nicolasatay102-ctrl
approved these changes
Oct 15, 2026
aabmass
approved these changes
Oct 15, 2026
braydonk
approved these changes
Oct 15, 2026
braydonk
left a comment
braydonk
left a comment
Contributor
There was a problem hiding this comment.
Weighing in since it might be tangentially related to the Batching Configuration Standardization project.
Environment variables aren't really on our radar as far as I know. I don't think this will conflict/impact anything we're working on as part of that project. Thanks!
Member
|
I'm neutral. |
pellared
reviewed
Oct 19, 2026
psx95
force-pushed
the
max-export-batch-size-env
branch
from
October 19, 2026 22:34
42a7fa5 to
26fde9d
Compare
pellared
approved these changes
Oct 20, 2026
Contributor
|
@dashpole We assigned this to you ;) |
5 of 8 tasks
1 of 6 tasks
pellared
pushed a commit
to pellared/opentelemetry-specification
that referenced
this pull request
Nov 3, 2026
…etry#5406) ## Changes Four changes merged after the `v1.62.0` tag were recorded under that release. Move them to the corresponding `Unreleased` subsections: - open-telemetry#5359: `OTEL_METRIC_EXPORT_MAX_BATCH_SIZE` environment variable. - open-telemetry#5363: optional ETW `etw.provider.name` mapping; also add its missing PR link. - open-telemetry#5368: identifying resource attributes in the Prometheus target info metric. - open-telemetry#5271: optional Sum handling in histogram conversion. Verified all 20 distinct PR references in `Unreleased` and `v1.62.0` against the `v1.61.0` and `v1.62.0` Git tags. The remaining `v1.62.0` entry text matches the release tag, and older release sections are unchanged. `git diff --check` passes. For non-trivial changes, follow the [change proposal process](https://github.com/open-telemetry/opentelemetry-specification/blob/main/CONTRIBUTING.md#proposing-a-change). * [ ] Related issues: N/A; changelog correction only. * [ ] Related [OTEP(s)](https://github.com/open-telemetry/oteps): N/A. * [ ] Links to the prototypes: N/A; no features or behavior changes. * [x] [`CHANGELOG.md`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/CHANGELOG.md) updated. * For trivial changes, include `[chore]` in the PR title to skip the changelog check. * [ ] [Spec compliance matrix](https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix/template.yaml): N/A. * [ ] [Declarative config data model](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/data-model.md#overview): N/A. > [!NOTE] > This PR and its description were prepared with OpenAI Codex. Co-authored-by: Carlos Alberto Cortez <calberto.cortez@gmail.com>
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
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.
Fixes #5358
Changes
Adds the
OTEL_METRIC_EXPORT_MAX_BATCH_SIZEenvironment variable to the Periodic exporting MetricReader section of the Environment Variable Specification to configure themaxExportBatchSizeoption (stabilized in #5291).For non-trivial changes, follow the change proposal process.
OTEL_METRIC_EXPORT_MAX_BATCH_SIZEenvironment variable for Periodic exporting MetricReader #5358CHANGELOG.mdfile updated for non-trivial changes[chore]in the PR title to skip the changelog check