-
Notifications
You must be signed in to change notification settings - Fork 888
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
Properly communicate the stability for OTLP #1147
Comments
Just wanted to make this point: it'd be good to have OTLP used in production with the understanding that at this point some portions of the proto may change drastically between releases, like From the conversation that evolved from the spec sig mtg today, perhaps documentation or blog posts may help in setting this expectation. |
I want to call out two things I think may send mixed signals:
|
Added a clarification for OTLP Logs: open-telemetry/opentelemetry-proto#228 |
We now have stability labels in both proto repo and in this repo in the "protocol" directory. I believe this issue is resolved. If any additional communication is needed please re-open or create a new issue that describes what else is needed. |
Based on feedback during the SIG call today, we need to be even more explicit about OTLP/protos still being in (relative) flux, and the fact it shouldn't be used in production systems these days. See https://github.com/open-telemetry/opentelemetry-proto#maturity-level - Also, there's the need to add Logs to this table, as either Experimental or Alpha.
Specially important as we are approaching Kubecon and we need to make things the community expectations are the proper ones ;)
cc @tigrannajaryan
The text was updated successfully, but these errors were encountered: