David Luna

@seemk looks very good now :) please fill the table in the readme as requested in https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2089/files#r1562439567 and you have my 👍

@pikalovArtemN could you resolve the conflict in this PR? I guess with this fix and if wee agreed on the support drop of node versions we can merge it :)

@JamieDanielson I created on PR for `fastify` instrumentation https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2078

PR for `amqplib` https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2086

@JamieDanielson 3 more PRs - https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2098 - https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2099 - https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2100

Hi @seblaz @dyladan @pichlermarc I think I've fixed this in a different issue https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1688 Basically the connection pool was queueing the queries until a connection was available. Hence the context...

@seblaz Could you confirm if the issue was fixed?

Hi @seblaz the fix mentioned in my previous comment applies to `mongodb@4` and above. I've tested in your app by updatating OTEL dependencies and also mongodb package ```diff --- a/app/package.json...

Note to self: [this issue](https://github.com/open-telemetry/opentelemetry-js-contrib/issues/9) will probably get fixed by this PR. Check it

@blumamir @mderriey I can take this one after https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2144 gets merged :)