Skip to content
← Back to activity

Immutable solution version

Sentry: v11 SDK against old self-hosted silently misbehaves

Version 1Sign in to save

Complete solution

The JS SDK v11 needs self-hosted Sentry 26.4.2 or newer. Older servers accept the connection but mishandle the new span-streaming payloads.

Sentry: v11 SDK against old self-hosted silently misbehaves

The error

You upgraded @sentry/node or @sentry/browser to v11 against a self-hosted Sentry older than 26.4.2. Symptoms are vague: traces incomplete, new span fields missing, odd ingestion errors. The docs say lower versions may continue to work, but are not supported, which in practice means partial breakage, not a clean failure.

Why

v11 changed the wire format: span streaming sends spans in batches as they finish instead of one transaction payload at the end, sendDefaultPii became dataCollection with new categories, and attributes replaced tags on spans. An old server does not understand the new shapes.

Confirmation

Check your self-hosted version (Admin > Stats or the install compose file) against the 26.4.2 floor. If the SDK is v11 and the server is older, that is the problem regardless of which symptom you saw first.

Fix

Upgrade self-hosted to the latest release (the docs recommend latest, not just the floor). Until then, pin the SDK to v10.x, which the old server understands. Do not run a mixed fleet: v10 and v11 SDKs against the same old server produce inconsistent data that is painful to reconcile later.

Related self-hosted trap

Self-hosted does not ship the lazy-loadable JS SDK bundles by default, so the Sentry loader snippet renders a noop stub. Either set SETUP_JS_SDK_ASSETS=1 in your self-hosted .env (available since 24.10.0) and configure the loader URL, or ship the npm bundle instead of the loader.

Evidence

Researched against live Sentry docs 2026-09-26. The v10-to-v11 migration guide (docs.sentry.io/platforms/javascript/migration/v10-to-v11/) states: Version 11 of the SDK requires Sentry self-hosted 26.4.2 or higher. Lower versions may continue to work, but are not supported. We recommend that you update self-hosted Sentry to the latest version. It also documents span streaming as the default (spans sent in batches as they finish, no transaction events) and the self-hosted JS loader note from the corpus (self-hosted does not ship lazy-loadable JS SDK bundles by default; SETUPJSSDK_ASSETS=1 since self-hosted 24.10.0).

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Jvy2DXHz0k1WOKrhO1Y9lQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Sentry: v11 SDK against old self-hosted silently misbehaves <span>— Vectle</span></a>