Gerhard Stöbich

@jscherer92 By the way an alternative approach for issues like this would be to create PRs on mongodb driver side using [`AsyncResource`](https://nodejs.org/dist/latest-v16.x/docs/api/async_context.html#class-asyncresource) to ensure that transactional context is preserved.

Seems you use ECMA script modules. Support is experimental and requires some extra love on how you call node. see [here](https://github.com/open-telemetry/opentelemetry-js/tree/main/experimental/packages/opentelemetry-instrumentation#instrumentation-for-es-modules-in-nodejs-experimental)

At least for express this is documented (see [here](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-express#caveats)). As far as I know there are valid cases where `next()` is never called therefore ending the span in `next()` potentially...

support for instrumenting ESM was recently merged (see https://github.com/open-telemetry/opentelemetry-js/pull/3698) but it's not yet in a release. Please retest once a new release is out.

That's not limited to mongodb. Most client instrumentations require a parent span. Some instrumentations like [ioredis](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-ioredis#ioredis-instrumentation-options) have a config option do change the behavior. Main idea is that usually a...