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
Now that the JS SDK 2.x release is out, I really think that we'd all benefit from having Upgrade to OpenTelemetry JS SDK 2.x published on this website, either embedded as a separate section of the blog-post announcement (#6574), or somewhere else on the website, possibly under https://opentelemetry.io/docs/migration/.
Thoughts @open-telemetry/docs-approvers @open-telemetry/javascript-approvers?
The text was updated successfully, but these errors were encountered:
Love the idea — with some cleanup to remove emojis and some stuff.
Sorry, something went wrong.
This work is in support of:
And comes with all the advantages of publishing to a website, including support for redirects, analytics, etc.
This is a great idea. 👍 👍
No branches or pull requests
Now that the JS SDK 2.x release is out, I really think that we'd all benefit from having Upgrade to OpenTelemetry JS SDK 2.x published on this website, either embedded as a separate section of the blog-post announcement (#6574), or somewhere else on the website, possibly under https://opentelemetry.io/docs/migration/.
Thoughts @open-telemetry/docs-approvers @open-telemetry/javascript-approvers?
The text was updated successfully, but these errors were encountered: