Clarify treatment of unspecified values in Metrics export pipeline #320
Labels
area:metrics
Part of OpenTelemetry Metrics
blocked:specification
Waiting on clarification of the OpenTelemetry specification before progress can be made
Milestone
This was discussed in #265, see this comment: #265 (comment)
The current otel-proto declares that unspecified values will be exported as empty strings. The question for the SDK is whether the exporters should be able to distinguish unspecified from empty strings. It could be accomplished by using the
core.Value
INVALID type, but the fix is not trivial because label encoders will need a way to represent unspecified.The text was updated successfully, but these errors were encountered: