Context:
Issue #803 noted that some JS instrumentations (specifically Fastify) were missing from the official opentelemetry.io registry and only appeared as third-party listings. That issue was opened in 2021 and partially addressed - but I want to do a current audit and submit any remaining missing packages.
What I'll do:
- Cross-reference all packages in
plugins/node/ against https://opentelemetry.io/registry/?language=js&component=instrumentation
- For each package not listed or listed as third-party: open a PR to
open-telemetry/opentelemetry.io with the correct registry entry (following the format in that repo's CONTRIBUTING guide)
- Specifically confirm
instrumentation-nestjs-core is correctly listed (I see it exists but want to verify the entry is up to date with the latest supported NestJS versions)
This is a small PR but keeps the registry accurate for the thousands of Node.js developers who discover instrumentations through the official registry. Is this straightforward to approve once I open the PR in the website repo?
Context:
Issue #803 noted that some JS instrumentations (specifically Fastify) were missing from the official opentelemetry.io registry and only appeared as third-party listings. That issue was opened in 2021 and partially addressed - but I want to do a current audit and submit any remaining missing packages.
What I'll do:
plugins/node/against https://opentelemetry.io/registry/?language=js&component=instrumentationopen-telemetry/opentelemetry.iowith the correct registry entry (following the format in that repo's CONTRIBUTING guide)instrumentation-nestjs-coreis correctly listed (I see it exists but want to verify the entry is up to date with the latest supported NestJS versions)This is a small PR but keeps the registry accurate for the thousands of Node.js developers who discover instrumentations through the official registry. Is this straightforward to approve once I open the PR in the website repo?