Valentin Marchaud

Oh i see, so yeah indeed, your setup is fine. I will create this and give you access. Can you come on http://slack.pm2.io so i can give you the secret...

No problem, i will be away the next hour also. Lets discuss on slack when you are available :)

I would like to bring an issue that i have found while playing with the runtime toggle of the trace events (via the inspector) : https://github.com/nodejs/node/issues/23185

We tried to play around at @keymetrics without success since it's not really documented in the V8 side either. From these research we believe the only use of this API...

> Hmm, time has passed... should any part of async_hooks be regarded as safe for use in production at this point? Note that the async hooks context manager in OTEL...

I'm not sure i understand exactly the problem here, do you want us to explain versions order ?

> Have you verified that we can implement these APIs with the existing context managers (AsyncHooks, zone.js)? If not this would be quite problematic. Looks doable to me for async...

> But I suppose that AsyncLocalStorageContextManager already utilized experimental APIs like AsyncLocalStorageContextManager.disable [[1]](https://github.com/open-telemetry/opentelemetry-js/blob/main/packages/opentelemetry-context-async-hooks/src/AsyncLocalStorageContextManager.ts?rgh-link-date=2022-06-27T02%3A31%3A19Z#L48) so it can be acceptable? I mean we started using ALC when it was still experiemental so...

> Added experimental tags to the docs and verified the rendered docs look as expected I think that's fine, i mean in the end people that want to use it...

> Another reasonable option might be to instead of Noop context manager use an extremely simple sync context manager. Well on web i don't see an issue (since there is...