Skip to content

docs: clarify view aggregation precedence #5342

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
naveenvenk17 wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −0
Open

docs: clarify view aggregation precedence #5342

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions opentelemetry-sdk/src/opentelemetry/sdk/metrics/_internal/view.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,11 @@ class View:
aggregation instance to use when data is aggregated for the
corresponding metrics stream. If `None` an instance of
`DefaultAggregation` will be used.
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

@aabmass aabmass Jun 22, 2026

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

`MetricReader` preferred aggregation is used.

exemplar_reservoir_factory: This is a metric stream customizing attribute:
the exemplar reservoir factory
Expand Down
Loading