Refine SDK MeterProvider configuration section (#3522)

Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
open-telemetry · Jun 14, 2023 · 37ab6b0 · 37ab6b0
1 parent d63b678
commit 37ab6b0
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 5 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -13,6 +13,9 @@ release.
 
 ### Metrics
 
+- Refine SDK MeterProvider configuration section.
+  ([#3522](/~https://github.com/open-telemetry/opentelemetry-specification/pull/3522))
+
 ### Logs
 
 ### Resource

diff --git a/specification/metrics/sdk.md b/specification/metrics/sdk.md
@@ -14,6 +14,7 @@ linkTitle: SDK
 - [MeterProvider](#meterprovider)
   * [MeterProvider Creation](#meterprovider-creation)
   * [Meter Creation](#meter-creation)
+  * [Configuration](#configuration)
   * [Shutdown](#shutdown)
   * [ForceFlush](#forceflush)
   * [View](#view)
@@ -112,11 +113,12 @@ When a Schema URL is passed as an argument when creating a `Meter` the emitted
 telemetry for that `Meter` MUST be associated with the Schema URL, provided
 that the emitted data format is capable of representing such association.
 
-Configuration (i.e., [MetricExporters](#metricexporter),
-[MetricReaders](#metricreader) and [Views](#view)) MUST be managed solely by the
-`MeterProvider` and the SDK MUST provide a way to configure all options that are
-implemented by the SDK. This MAY be done at the time of MeterProvider creation
-if appropriate.
+### Configuration
+
+Configuration (i.e. [MetricExporters](#metricexporter),
+[MetricReaders](#metricreader) and [Views](#view)) MUST be owned by the
+`MeterProvider`. The configuration MAY be applied at the time of `MeterProvider`
+creation if appropriate.
 
 The `MeterProvider` MAY provide methods to update the configuration. If
 configuration is updated (e.g., adding a `MetricReader`), the updated