We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/telemetry-stability.md
Such instrumentations are prohibited from changing any produced telemetry.
and
After the moratorium is lifted, stable instrumentations are allowed to change the produced telemetry if all the following conditions are fulfilled: The change is part of OpenTelemetry semantic conventions and is in a released version of the specification. The change has a corresponding published OpenTelemetry Schema File that describes the change. The produced telemetry correctly specifies the respective Schema URL.
After the moratorium is lifted, stable instrumentations are allowed to change the produced telemetry if all the following conditions are fulfilled:
I think it we should explicitly callout that changes related to bugfixes and security patches are allowed.
Related to:
CC @trask , @lmolkova , @CodeBlanch
The text was updated successfully, but these errors were encountered:
It might be closed because of open-telemetry/semantic-conventions#860 (comment)
However, it may be worth to make it more clear or change some wording as e.g.
Such instrumentations are prohibited from changing any produced telemetry
gives an impression that nothing can be changed.
Sorry, something went wrong.
No branches or pull requests
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/telemetry-stability.md
and
I think it we should explicitly callout that changes related to bugfixes and security patches are allowed.
Related to:
CC @trask , @lmolkova , @CodeBlanch
The text was updated successfully, but these errors were encountered: