Skip to content
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

Clarify OTLP stability #1397

Closed
tedsuo opened this issue Feb 3, 2021 · 0 comments · Fixed by #1400
Closed

Clarify OTLP stability #1397

tedsuo opened this issue Feb 3, 2021 · 0 comments · Fixed by #1400
Labels
area:sdk Related to the SDK priority:p2 Medium priority level release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:miscellaneous For issues that don't match any other spec label spec:protocol Related to the specification/protocol directory

Comments

@tedsuo
Copy link
Contributor

tedsuo commented Feb 3, 2021

Currently the OTLP specification is a mix of stable and experimental sections. Some of these sections are mixed together to the point that it is hard to clarify what is stable vs what is experimental. For example:

  • Proto over HTTP is stable, while JSON over HTTP is experimental.
  • The tracing protocol is stable, while the metrics protocol is experimental.

This document should be reformatted to more clearly separate the stable and experimental sections.

@tedsuo tedsuo added the spec:miscellaneous For issues that don't match any other spec label label Feb 3, 2021
@carlosalberto carlosalberto added area:sdk Related to the SDK release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:protocol Related to the specification/protocol directory priority:p2 Medium priority level labels Feb 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:sdk Related to the SDK priority:p2 Medium priority level release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:miscellaneous For issues that don't match any other spec label spec:protocol Related to the specification/protocol directory
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants