Pino instrumentation fails when using ES modules

[nlindley]

What version of OpenTelemetry are you using?

• @opentelemetry/api: 1.4.1
• @opentelemetry/instrumentation: 0.41.0
• @opentelemetry/instrumentation-pino: 0.34.0
• @opentelemetry/sdk-node: 0.41.0
• @opentelemetry/sdk-trace-base: 1.15.0

What version of Node are you using?

18.16.1

What did you do?

Attempted to instrument pino using either default or named imports.

What did you expect to see?

Trace information in the logs.

What did you see instead?

When using default imports, the application crashes when pino() is called. When using named imports, trace information is not added to the logs.

Additional context

We have minimal reproductions of the issues:

• Default import: https://github.com/nlindley/otel-esm-examples/tree/master/pino-default
• Named import: https://github.com/nlindley/otel-esm-examples/tree/master/pino-named

[dyladan]

I think this is the same as open-telemetry/opentelemetry-js#3976

For now you may be able to just use the previous version until we can provide a fix.

[klippx]

They reverted open-telemetry/opentelemetry-js#4011 maybe you should do the same?

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[jacobwood091]

This appears to still be an issue. We may want to look towards a solution such as that proposed by #1694, as this seems to be a resolution difference within the ECMAScript Module Namespace Object versus that of the CommonJS resolved Namespace. This comment, especially the Aside, provides an excellent analysis relevant to the underlying issue.