@sentry/effect server moved from @sentry/node-core/light to full @sentry/node in the node-core merge (#22418). Light mode installed an AsyncLocalStorage async-context strategy that matched Effect's fiber model, so SentryEffectTracer spans became the http.server GET transaction. Full @sentry/node installs the OpenTelemetry context strategy instead, and the Effect tracer's span context no longer propagates across the HTTP request boundary, so no transaction is emitted.
The server transaction e2e tests in effect-3-node / effect-4-node are currently marked test.fixme (errors + logs still pass). We need to adapt Effect's server tracing to the full-node context model and re-enable them.
This is expected to be unblocked by #22486 (no-tracer-provider default + AsyncLocalStorage context strategy in @sentry/node).
Acceptance criteria
- Effect server tracing produces the root transaction again (or an intentionally revised, documented shape).
- Un-
fixme the transaction e2e tests in dev-packages/e2e-tests/test-applications/effect-{3,4}-node/tests/transactions.test.ts.
@sentry/effectserver moved from@sentry/node-core/lightto full@sentry/nodein the node-core merge (#22418). Light mode installed an AsyncLocalStorage async-context strategy that matched Effect's fiber model, soSentryEffectTracerspans became thehttp.server GETtransaction. Full@sentry/nodeinstalls the OpenTelemetry context strategy instead, and the Effect tracer's span context no longer propagates across the HTTP request boundary, so no transaction is emitted.The server transaction e2e tests in
effect-3-node/effect-4-nodeare currently markedtest.fixme(errors + logs still pass). We need to adapt Effect's server tracing to the full-node context model and re-enable them.This is expected to be unblocked by #22486 (no-tracer-provider default + AsyncLocalStorage context strategy in
@sentry/node).Acceptance criteria
fixmethe transaction e2e tests indev-packages/e2e-tests/test-applications/effect-{3,4}-node/tests/transactions.test.ts.