Roch Devost

This is because we use these modules but only when they are available. If you are not using GraphQL and these modules are not available, it's safe to compile without...

For now it would have to be done manually. For databases, this would best be done in a custom client that wraps the real ODBC client to intercept and trace...

@chris-chao Do you get the same memory increase if profiling is disabled and only tracing is enabled?

> Is it something that is being worked on? We've been looking into using Undici for sending traces, but we haven't looked into writing a plugin for it yet. >...

@flovilmart It should be based on the `undici` version, but the Node version shouldn't matter since in older versions the module will not exist so the plugin will simply never...

@flovilmart Actually it's fine if the implementation in Undici is backed 100% by diagnostics channel. My thought was that we need to do the monkey-patching anyway to support older versions...

> Notably, the next tests seem to fails because of the inclusion of the diagnostic_channels module. Any guidance on the workaround? @flovilmart Not sure why these would interact. Can you...

We're actually in the process of finalizing the approach of instrumenting with `async_hooks` and `diagnostics_channel` now that we have rewritten 50+ plugins and put it to the test, so might...

Quick update related to the above: we're currently finishing up the new approach which we'll be trying internally in the next few weeks, and we plan to add instrumentation to...

This library is able to inject the tracing context into your logs in order to correlate between traces and logs, but it doesn't actually send the logs on its own....