feat(auto-instrumentations-node, instrumentation-fastify)!: remove instrumentation-fastify#3409
Conversation
…strumentation-fastify In favor of "@fastify/otel". instr-fastify had been deprecated back in Jan 2025 and planned for removal in Jun 2025. Refs: open-telemetry#2651
raphael-theriault-swi
left a comment
There was a problem hiding this comment.
I think component_owners.yaml and GUIDELINES.md may still have some mentions of the instrumentation but otherwise LGTM
Thanks. I think I got those in my second commit. |
Nope. @raphael-theriault-swi was right, I missed some. Removed those refs in commit 477ed20 |
|
This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature. |
|
When this is merged/released there are a couple other issues that could likely be closed: https://github.com/open-telemetry/opentelemetry-js-contrib/issues?q=state%3Aopen%20label%3Apkg%3Ainstrumentation-fastify |
…metry/opentelemetry-js-contrib#3409) Signed-off-by: Vitor Vasconcellos <vvasconcellos1@gmail.com>
Upstream has dropped instrumentation-fastify, so we are as well. The test case has changed to verify that using EDOT Node.js and the 3rd-party @fastify/otel works. Refs: open-telemetry/opentelemetry-js-contrib#3409
Upstream has dropped instrumentation-fastify, so we are as well. The test case has changed to verify that using EDOT Node.js and the 3rd-party @fastify/otel works. Refs: open-telemetry/opentelemetry-js-contrib#3409
In favor of "@fastify/otel". instr-fastify had been deprecated back
in Jan 2025 and planned for removal in Jun 2025.
Refs: #2651
Refs: #2647