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
Hi!
I recently worked with opentelemetry-specification to align on a standardized naming for instrumentations across languages. Here's the final result:
https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/overview.md#instrumentation-libraries
And the PR where it was discussed:
open-telemetry/opentelemetry-specification#539
I think if go followed the specification as written, it would have packages renamed from "plugin" to "instrumentation":
https://github.com/open-telemetry/opentelemetry-go/tree/master/plugin
I'm filing this issue for awareness and discussion, and happy to collect and raise questions to the spec or technical committee.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Hi!
I recently worked with opentelemetry-specification to align on a standardized naming for instrumentations across languages. Here's the final result:
https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/overview.md#instrumentation-libraries
And the PR where it was discussed:
open-telemetry/opentelemetry-specification#539
I think if go followed the specification as written, it would have packages renamed from "plugin" to "instrumentation":
https://github.com/open-telemetry/opentelemetry-go/tree/master/plugin
I'm filing this issue for awareness and discussion, and happy to collect and raise questions to the spec or technical committee.
The text was updated successfully, but these errors were encountered: