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 js followed the specification as written, it would have a small set of renamed:
I wanted to raise this as a discussion as well as possibly a "bug": main question is: does this specification as written work for js?
The text was updated successfully, but these errors were encountered:
sorry I don't have permissions, but this probably better warrants the "discussion" tag.
Sorry, something went wrong.
While there are only 4 packages here, there are 8 in node contrib and 2 in web contrib.
Additional discussion around this in open-telemetry/opentelemetry-js-contrib#37
This is done no? @dyladan
docs: Document how to ignore Express routes (open-telemetry#1095)
11ab701
No branches or pull requests
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 js followed the specification as written, it would have a small set of renamed:
I wanted to raise this as a discussion as well as possibly a "bug": main question is: does this specification as written work for js?
The text was updated successfully, but these errors were encountered: