how would it work with zero-code-change instrumentation pattern?

[liesislukas]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the issue has not already been raised

Issue

Currently, this package requires importing from the OpenTelemetry instrumentation file, which makes it impossible to use in zero-code change instrumentation setups. Zero-code change instrumentation is a common approach in many Node.js libraries, as well as across the broader OpenTelemetry ecosystem.

Typically, OpenTelemetry libraries are controlled via environment variables, rather than requiring direct imports or manual plugin configuration.

I wanted to integrate this package into @otelic/open-telemetry, which provides zero-code change instrumentation. However, this doesn’t seem possible with the current API.

Am I missing something?
Is there a recommended approach to achieve this?
Or would supporting auto-instrumentation (e.g., via environment variables) be something to consider?

Thanks

[liesislukas]

btw, at the moment https://otelic.com package is using @opentelemetry/instrumentation-fastify because of issues above

[metcoder95]

@fastify/otel started with no module patching design on mind, seeking to take direct advantage of the plugin system from fastify to properly instrument each part of a fastify application.

This approach has the benefit of a less intrusive and compatible instrumentation for fastify at a cost of dropping the zero-code change instrumentation.

I'm a bit over the fence for the auto-instrumentation, although I'd consider it in a way that is not the default and not the path we recommend to take.

[metcoder95]

#22 should cover the issue