@@ -25,7 +25,6 @@ Table of Contents
25
25
* [ MeterProvider] ( #meterprovider )
26
26
* [ Attribute Limits] ( #attribute-limits )
27
27
* [ MeasurementProcessor] ( #measurementprocessor )
28
- * [ MetricProcessor] ( #metricprocessor )
29
28
* [ MetricExporter] ( #metricexporter )
30
29
* [ Push Metric Exporter] ( #push-metric-exporter )
31
30
* [ Pull Metric Exporter] ( #pull-metric-exporter )
@@ -44,13 +43,13 @@ to create an
44
43
instance which is stored on the created ` Meter ` .
45
44
46
45
Configuration (i.e., [ MeasurementProcessors] ( #measurementprocessor ) ,
47
- [ MetricProcessors ] ( #metricprocessor ) , [ MetricExporters ] ( #metricexporter ) and
48
- [ ` Views ` ] ( #view ) ) MUST be managed solely by the ` MeterProvider ` and the SDK MUST
49
- provide a way to configure all options that are implemented by the SDK. This MAY be done at the
50
- time of MeterProvider creation if appropriate.
46
+ [ MetricExporters ] ( #metricexporter ) and [ ` Views ` ] ( #view ) ) MUST be managed solely
47
+ by the ` MeterProvider ` and the SDK MUST provide a way to configure all options
48
+ that are implemented by the SDK. This MAY be done at the time of MeterProvider
49
+ creation if appropriate.
51
50
52
51
The ` MeterProvider ` MAY provide methods to update the configuration. If
53
- configuration is updated (e.g., adding a ` MetricProcessor ` ), the updated
52
+ configuration is updated (e.g., adding a ` MeasurementProcessor ` ), the updated
54
53
configuration MUST also apply to all already returned ` Meters ` (i.e. it MUST NOT
55
54
matter whether a ` Meter ` was obtained from the ` MeterProvider ` before or after
56
55
the configuration change). Note: Implementation-wise, this could mean that
@@ -256,31 +255,6 @@ active span](../trace/api.md#context-interaction)).
256
255
+------------------+
257
256
```
258
257
259
- ## MetricProcessor
260
-
261
- ` MetricProcessor ` is an interface which allows hooks for [ pre-aggregated metrics
262
- data] ( ./datamodel.md#timeseries-model ) .
263
-
264
- Built-in metric processors are responsible for batching and conversion of
265
- metrics data to exportable representation and passing batches to exporters.
266
-
267
- The following diagram shows ` MetricProcessor ` 's relationship to other components
268
- in the SDK:
269
-
270
- ``` text
271
- +-----------------+ +-----------------+ +-----------------------+
272
- | | Metrics... | | Metrics... | |
273
- | In-memory state +------------> MetricProcessor +------------> MetricExporter (push) +--> Another process
274
- | | | | | |
275
- +-----------------+ +-----------------+ +-----------------------+
276
-
277
- +-----------------+ +-----------------+ +-----------------------+
278
- | | Metrics... | | Metrics... | |
279
- | In-memory state +------------> MetricProcessor +------------> MetricExporter (pull) +--> Another process (scraper)
280
- | | | | | |
281
- +-----------------+ +-----------------+ +-----------------------+
282
- ```
283
-
284
258
## MetricExporter
285
259
286
260
` MetricExporter ` defines the interface that protocol-specific exporters MUST
@@ -291,6 +265,23 @@ The goal of the interface is to minimize burden of implementation for
291
265
protocol-dependent telemetry exporters. The protocol exporter is expected to be
292
266
primarily a simple telemetry data encoder and transmitter.
293
267
268
+ The following diagram shows ` MetricExporter ` 's relationship to other components
269
+ in the SDK:
270
+
271
+ ``` text
272
+ +-----------------+ +-----------------------+
273
+ | | Metrics... | |
274
+ | In-memory state +------------> MetricExporter (push) +--> Another process
275
+ | | | |
276
+ +-----------------+ +-----------------------+
277
+
278
+ +-----------------+ +-----------------------+
279
+ | | Metrics... | |
280
+ | In-memory state +------------> MetricExporter (pull) +--> Another process (scraper)
281
+ | | | |
282
+ +-----------------+ +-----------------------+
283
+ ```
284
+
294
285
Metric Exporter has access to the [ pre-aggregated metrics
295
286
data] ( ./datamodel.md#timeseries-model ) .
296
287
0 commit comments