Skip to content

docs: clarify view aggregation precedence#5342

Open
naveenvenk17 wants to merge 1 commit into
open-telemetry:mainfrom
naveenvenk17:naveenvenk17/otel/document-view-aggregation-precedence
Open

docs: clarify view aggregation precedence#5342
naveenvenk17 wants to merge 1 commit into
open-telemetry:mainfrom
naveenvenk17:naveenvenk17/otel/document-view-aggregation-precedence

Conversation

@naveenvenk17

Copy link
Copy Markdown

Summary

  • Document how View aggregation interacts with MetricReader preferred aggregation.
  • Clarify that a concrete, non-DefaultAggregation view aggregation takes precedence, while DefaultAggregation lets the reader preferred aggregation apply.

Validation

  • git diff --check
  • python -m compileall opentelemetry-sdk\src\opentelemetry\sdk\metrics\_internal\view.py

Closes #2834.

@naveenvenk17 naveenvenk17 requested a review from a team as a code owner June 22, 2026 17:23
When a view matches an instrument, a non-`DefaultAggregation`
aggregation configured on the view takes precedence over the
`MetricReader` preferred aggregation for that instrument class. If
the view leaves aggregation as `DefaultAggregation`, the

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.

This second sentence feels like an implementation detail we can leave out of documentation for now, unless that behavior is explicitly in the spec. Do you mind double checking

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

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Add a docstring to outline metric reader and view configuration conflicts

2 participants