-
Notifications
You must be signed in to change notification settings - Fork 896
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
Move specification for implementations of the metric API into own specification #3171
Conversation
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.
I'm very supportive of these changes. I think having the behavior you're moving out of the API specification caused some confusion and implementation friction, particularly for python.
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.
This looks great! Just nits
Co-authored-by: David Ashpole <[email protected]>
Co-authored-by: Anthony Mirabella <[email protected]>
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.
Couple minor comments but looks good. Thanks!
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.
I have read it twice. Nice improvement.
Merged. Follow up question - do we think tracing and logging spec should do the same? |
I think so. We should probably open an issue to track this work. |
@reyang I can open an issue unless you have already started one. Let me know. |
I haven't, please go ahead. |
Contributes to #3268. @MrAlias did some good work in the metrics API / SDK recently in #3171 and #3067 to ensure that the metrics API spec doesn't contain SDK implementation details. This PR adopts similar language in the Logs Bridge API / SDK documents, which includes breaking out a `noop.md` document.
…API (#3890) The api.md document specifies the Metric API, it does not defined the OpenTelemetry defined implementations of this API. Remove or correct the details within this API and leave it for the implementation specification to define. Importantly, the API is decoupled from implementation for a reason. Third-party implementation may exists that OTel does not have domain over. This document needs to written with that in mind. Related to #3171 and #3071.
…elemetry#3275) Contributes to open-telemetry#3268. @MrAlias did some good work in the metrics API / SDK recently in open-telemetry#3171 and open-telemetry#3067 to ensure that the metrics API spec doesn't contain SDK implementation details. This PR adopts similar language in the Logs Bridge API / SDK documents, which includes breaking out a `noop.md` document.
…API (open-telemetry#3890) The api.md document specifies the Metric API, it does not defined the OpenTelemetry defined implementations of this API. Remove or correct the details within this API and leave it for the implementation specification to define. Importantly, the API is decoupled from implementation for a reason. Third-party implementation may exists that OTel does not have domain over. This document needs to written with that in mind. Related to open-telemetry#3171 and open-telemetry#3071.
Fixes #3071
Fixes #3072
Changes
sdk.md
api.md
noop.md
to defined the metric No-Op implementation of the metric APIIn the reshuffle, this clarified ...
Outside of these clarifications, all changes should be editorial.