opentelemetry-proto
opentelemetry-proto copied to clipboard
Metrics Number data points requirements for value
Define if it is an error or not to receive for the same "Resource, InstrumentationLibrary, MetricName, Labels/Attributes, StartTime" first point with int value and next point with double value.
We need to document this behavior.
Copying from Slack to make sure it's not lost: OM considers it non-breaking, but not something that should happen frequently: https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#exposition-across-time-and-metric-evolution
We discussed this in the Metrics Data Model SiG.
- Based on previous discussion we don't think this is blocking declaring our API sstable.
- We should specify what is allowable within a collector ("on the wire"), specifically around aggregations.
We had talked about a notion of "weak conformance" that allows migrating int to double when this situation occurs. Specification remains TBD.