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
This is not a bug. We can comment on this in the data model specification.
While it is expected that a metric stream of "int" would have its measurements comprised of "int" as well (so exemplar + data point line up), it's not a requirement on the protocol.
Think this is worth opening some more language to outline what happens here, e.g. "services are free to convert double -> long" in that instance.
Right now it is possible to construct a Gauge or Sum that contains a NumberDataPoint value with as "int" see:
https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/metrics/v1/metrics.proto#L339
and an Exemplar associated with that point that has a "double" value see https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/metrics/v1/metrics.proto#L533
Is this considered a bug? What should a service do when this case happens?
The text was updated successfully, but these errors were encountered: