You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all - I was wondering what the best way to instrument the WebApp.connectHandlers provided by meteor. We use these connectHandlers to expose different webhooks, yet I don't see any tracing related to a connect service that I expect to see. Given that this seems to just be a wrapper around connect, I'm wondering why the built in dd-trace connect instrumentation does not work in this case. I'm guessing this must be due to some misunderstanding I have with the way dd-trace monkey-patches different packages. For context, I'm well aware of the inherent incompatibility that Meteor has with dd-trace due to the Fibers <> async_hooks incompatibility: #1229; that being said, I don't believe my current question should be affected by this.
I'm happy to provide more context here, just let me know what would be good to know.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi all - I was wondering what the best way to instrument the
WebApp.connectHandlers
provided by meteor. We use these connectHandlers to expose different webhooks, yet I don't see any tracing related to a connect service that I expect to see. Given that this seems to just be a wrapper around connect, I'm wondering why the built in dd-trace connect instrumentation does not work in this case. I'm guessing this must be due to some misunderstanding I have with the way dd-trace monkey-patches different packages. For context, I'm well aware of the inherent incompatibility that Meteor has with dd-trace due to the Fibers <> async_hooks incompatibility: #1229; that being said, I don't believe my current question should be affected by this.I'm happy to provide more context here, just let me know what would be good to know.
Thanks!
The text was updated successfully, but these errors were encountered: