-
Notifications
You must be signed in to change notification settings - Fork 897
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
DataPoint Flags are not mentioned in the Metrics Data Model #4053
Comments
In the GC triage session we thought this was an interesting question that warranted TC attention:
|
@pyohannes @zeitlinger As both of you have approached this topic from the perspective of how to report timeseries deletion, I'd like to involve you in thinking about how to update the data model to define how the flags fit the model. |
Thanks for the ping, I had missed it, looks good to me! |
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.
Fixes open-telemetry#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.
What are you trying to achieve?
I am working with the staleness marker added in open-telemetry/opentelemetry-proto/pull/316. It seems to be available on the proto, but not the data model.
What did you expect to see?
The staleness marker or datapoint flags more generally mentioned in the data model.
Additional context.
I guess what confuses me here is what the relationship between the proto and the data model is. Is the proto meant to be a superset of the data model? How should I interpret the semantics of fields present on the proto but not on the data model?
The text was updated successfully, but these errors were encountered: