You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you configure the metrics basic.Processor with an AggregationTemporalitySelector that disagrees with the configured Exporter, it's possible for the exporter to receive the wrong data and no error message.
I observed this with the following configuration:
basic.Processor given a StatelessAggregationTemporalitySelector (a.k.a. StatelessExportKindSelector).
Prometheus exporter used, this exporter will see deltas and no error messages.
This should return errors to the exporter. After View Configuration is implemented, it should not be possible to arrive in this configuration. See open-telemetry/opentelemetry-specification#2013
The text was updated successfully, but these errors were encountered:
This issues relates to the current metric SDK. The metric SDK redesign project includes changes to the SDK design that will make this issue obsolete. I'm closing so no wasted work is performed to address this.
Description
When you configure the metrics
basic.Processor
with an AggregationTemporalitySelector that disagrees with the configured Exporter, it's possible for the exporter to receive the wrong data and no error message.I observed this with the following configuration:
basic.Processor
given aStatelessAggregationTemporalitySelector
(a.k.a. StatelessExportKindSelector).Related: #2274.
Expected behavior
This should return errors to the exporter. After View Configuration is implemented, it should not be possible to arrive in this configuration. See open-telemetry/opentelemetry-specification#2013
The text was updated successfully, but these errors were encountered: