From ee5291498ccf67f4ea98ea348d00f6845b2fa597 Mon Sep 17 00:00:00 2001 From: naveenvenk17 Date: Mon, 22 Jun 2026 22:53:34 +0530 Subject: [PATCH] docs: clarify view aggregation precedence --- .../src/opentelemetry/sdk/metrics/_internal/view.py | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/opentelemetry-sdk/src/opentelemetry/sdk/metrics/_internal/view.py b/opentelemetry-sdk/src/opentelemetry/sdk/metrics/_internal/view.py index 7eb1fcc728e..039109d8409 100644 --- a/opentelemetry-sdk/src/opentelemetry/sdk/metrics/_internal/view.py +++ b/opentelemetry-sdk/src/opentelemetry/sdk/metrics/_internal/view.py @@ -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 + `MetricReader` preferred aggregation is used. exemplar_reservoir_factory: This is a metric stream customizing attribute: the exemplar reservoir factory