-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add optional data point flags to all metrics data points, support staleness markers #316
Conversation
@bogdandrutu @open-telemetry/specs-metrics-approvers Please take a look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, except one question:
In protobuf is the enum equivalent with an "int32"? If not how would we intend to add new values? An enum has the property that only one value can be sent, if we add a new bit "foo" then are we going to change them to 4 new values NO_FOO_NONE, NO_FOO_NO_RECORD, FOO_NONE, etc.?
Do we need the value in the points to be uint32 and the enum be the bitset mask? Probably I am missing something...
@jmacd also this needs a rebase |
Yes, see https://developers.google.com/protocol-buffers/docs/proto3#enum |
I switched this to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Last comment :)
🎉 |
Fixes #4053 ## Changes This PR extends the metric data model with data point flags, which were added to the protocol in open-telemetry/opentelemetry-proto#316.
Adds a bit to represent stale points they way Prometheus does when scraping for metrics yields no results. This avoids the use of IEEE 754 NaN values in data points that do not necessarily have a floating point field that can be used.
Resolves #315.
Related: open-telemetry/opentelemetry-specification#1078
Partial copy from #310.
Resolves #309.