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
We currently already ship some auto-performance instrumentation with @sentry/node. Now that things have stabilised a bit, we want to expand support and add further instrumentation. There are some low hanging fruits, in OTEL instrumentation that exists that we can leverage.
The text was updated successfully, but these errors were encountered:
stephanie-anderson
changed the title
Add additional Node Auto Instrumentation
[JavaScript] Increase auto instrumentation for Node.js
Sep 25, 2024
mydea
changed the title
[JavaScript] Increase auto instrumentation for Node.js
[JavaScript] Implement more auto instrumentation for Node.js
Sep 26, 2024
Related to #13317
Improve the docstrings and link to documentation pages as appropriate
(as they contain information about opentelemetry and supported
versions).
We decided against including socket io instrumentation because of some concerns about long running spans in the sdk, and the fact that we don't have websockets well specced out in general in Sentry's tracing model.
The only things left are Express v5 and Firebase. Express v5 is being actively worked on, we're going to rely on diagnostics channels to do it, just need upstream work for it. Firebase PR is WIP, but I think it can be worked on past this issue.
There'a also the vercel AI work which is tracked here: #13679
Once we merge in Vercel AI and do the next release of the SDK, I'll be closing this issue. Express 5, firebase, the dataloader fix can be tracked outside of this issue.
Description
We currently already ship some auto-performance instrumentation with
@sentry/node
. Now that things have stabilised a bit, we want to expand support and add further instrumentation. There are some low hanging fruits, in OTEL instrumentation that exists that we can leverage.The text was updated successfully, but these errors were encountered: