Clarify that MetricReader has one-to-one mapping to MeterProvider (#2406

)
open-telemetry · Mar 11, 2022 · 660826e · 660826e
1 parent 44c1acd
commit 660826e
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 0 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -31,6 +31,8 @@ release.
 - Clarify that the periodic metric reader is the default metric reader to be
   paired with push metric exporters (OTLP, stdout, in-memory)
   ([#2379](https://github.com/open-telemetry/opentelemetry-specification/pull/2379)).
+- Clarify that MetricReader has one-to-one mapping to MeterProvider.
+  ([#2406](https://github.com/open-telemetry/opentelemetry-specification/pull/2406)).
 
 ### Logs
 

diff --git a/specification/metrics/sdk.md b/specification/metrics/sdk.md
@@ -652,6 +652,9 @@ that SDK will update the time range - e.g. from (T<sub>n</sub>, T<sub>n+1</sub>]
 to (T<sub>n+1</sub>, T<sub>n+2</sub>] - **ONLY** for this particular
 `MetricReader` instance.
 
+The SDK MUST NOT allow a `MetricReader` instance to be registered on more than
+one `MeterProvider` instance.
+
 ```text
 +-----------------+            +--------------+
 |                 | Metrics... |              |