Document that setting skipOpenTelemetrySetup: true breaks error tracking

[punkpeye]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/node

SDK Version

10.30.0

Framework Version

No response

Link to Sentry event

No response

Reproduction Example/SDK Setup

N/A

Steps to Reproduce

Set skipOpenTelemetrySetup

Expected Result

Errors associated with their scope (e.g. Fastify requests).

Actual Result

Errors are not associated with their scope.

Additional Context

It should be safe to disable skipOpenTelemetrySetup, but clearly it isn't.

So at least please document that that's the case.

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1311

[s1gr1d]

Hello, did you set up OTel alongside Sentry like documented here?

[punkpeye]

No. I wanted to disable OTEL instrumentation.

But it is not documented anywhere that disabling OTEL (which is desired due to performance reasons) will break Sentry's ability to associate errors with AsyncContext.

[s1gr1d]

It's documented that you need a custom OTel setup for this as this will manage the context. I'll make that more clear in the docs.