Support non-buffered Server-Sent Events (SSE) responses in the Node.js SDK

[ivan-jimmai]

Problem Statement

We operate a real-time AI chat platform (LibreChat-based) that streams LLM responses to clients using Server-Sent Events (SSE).

When the Sentry Node.js SDK (@sentry/node) is initialized, SSE responses stop streaming incrementally and instead appear to be buffered, causing the client UI to hang or fail to display tokens in real time.

If Sentry initialization is removed entirely, SSE streaming works correctly.

We have confirmed:

• The issue affects Express-based SSE endpoints
• It occurs even when streaming routes are fully excluded from:
  Transactions
  Spans
  Events
  Profiling
• The behavior suggests response buffering occurs before route-level filtering is applied
  This makes it currently impossible to use Sentry in production for applications that rely on long-lived SSE connections (e.g., AI token streaming).

Solution Brainstorm

Potential approaches that would enable safe SSE support:

1. Opt-out of response buffering
   A global or per-route option to disable any response buffering or wrapping behavior in the Node SDK.
2. SSE-aware HTTP instrumentation
   Detect Content-Type: text/event-stream and bypass any logic that intercepts or delays writes to res.
3. Dedicated streaming-safe integration
   A lightweight HTTP integration mode for long-lived streaming responses that:
   - Captures errors only
   - Avoids transaction lifecycle tracking tied to response completion
4. Official best-practice guidance
   Document a recommended pattern for monitoring SSE / AI streaming endpoints without breaking real-time delivery.

Additional Context

• Stack: Node.js + Express
• Streaming protocol: Server-Sent Events (SSE)
• Use case: Real-time AI / LLM token streaming
• Related discussion: Performance Monitoring for Web Streams (Response API) #9633
• We attempted extensive route exclusions (ignoreTransactions, beforeSend, beforeSendTransaction, shouldCreateSpanForRequest) with no success, indicating buffering happens prior to those hooks.

This issue significantly limits Sentry adoption for modern AI platforms where streaming is a core requirement.

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-1499

[RulaKhaled]

Hello @ivan-jimmai, thanks for reaching out. We will try to reproduce this, meanwhile:

Can you confirm whether you’re using OpenAI (internally) or any of the packages listed here?
https://docs.sentry.io/platforms/javascript/guides/node/tracing/instrumentation/ai-agents-module/#automatic-instrumentation

If so, you can disable the integration causing this error by filtering it out in Sentry.init():

integrations: (integrations) => {
  // integrations.push(Sentry.browserTracingIntegration()); <- no need to add this
  return integrations.filter((i) => i.name !== "OpenAI");
},

[RulaKhaled]

Can you please provide the SDK version you’re using and a minimal reproduction? I haven’t been able to reproduce this

[ivan-jimmai]

Hi, @RulaKhaled
Thanks for your reply.
This is our env:

• Sentry SDK Versions:
  • @sentry/node: ^10.32.1
  • @sentry/profiling-node: ^10.32.1
  • @sentry/react: ^10.32.1 (frontend, not directly related to this issue)
• Node.js Version: 20.19.6
• LangGraph Version: (via @librechat/agents: ^3.0.66)
• Framework: Express.js

We confirmed the main issue is that:
Sentry v10's async hooks prevent LangGraph event handlers from being called. Handlers are registered correctly but never invoked during processStream execution.

Minimal Reproduction:

const Sentry = require('@sentry/node');
Sentry.init({ dsn: 'your-dsn' });

// Register handler with LangGraph
const handlers = {
  [GraphEvents.ON_MESSAGE_DELTA]: {
    handle: (event, data) => {
      console.log('Handler called'); // Never appears after Sentry init
    },
  },
};

await run.processStream({ messages }, config, { customHandlers: handlers });
// Handler never called, but processStream completes successfully

What We Tried:

• Sentry.withIsolationScope() - No effect
• Disabling HTTP tracing - No effect
• Setting tracesSampleRate: 0.0 - No effect
• Clearing spans/scopes - No effect
• Using setImmediate to break async context - No effect

Expected vs Actual:
Expected: Handlers execute synchronously when LangGraph emits events
Actual: Handlers never called, events silently dropped