-
Notifications
You must be signed in to change notification settings - Fork 887
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
Determine how to report dropped metrics #1655
Labels
area:data-model
For issues related to data model
area:semantic-conventions
Related to semantic conventions
enhancement
New feature or request
spec:metrics
Related to the specification/metrics directory
Comments
jsuereth
added
enhancement
New feature or request
area:semantic-conventions
Related to semantic conventions
spec:metrics
Related to the specification/metrics directory
area:data-model
For issues related to data model
labels
Apr 27, 2021
Context (in note form)
Open Questions
|
|
Copying the message from #2960 as this looks like the right place to discuss it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:data-model
For issues related to data model
area:semantic-conventions
Related to semantic conventions
enhancement
New feature or request
spec:metrics
Related to the specification/metrics directory
In #1618, the question of who to handle "dropped" metrics within OTLP was asked. In that PR, a naive algorithm for Delta => Cumulative sum conversion was proposed that was intended to be lightweight (in memory consumption) and does NOT allow for out-of-order (or delayed) delta sum points.
This raises the question of how you would report "dropped" metrics within OTLP for this scenario. Do we want to provide some known (semantic) convention? Or should this be a first class attribute (like dropped_attribute_count on spans)?
For now, tagging this as DataModel + Semantic convention until we've had a chance to discuss the best way to handle this.
The text was updated successfully, but these errors were encountered: