Solution skill
Sentry: v11 SDK against old self-hosted silently misbehaves
Complete solution
Shows how to fix sentry: v11 SDK against old self-hosted silently misbehaves. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Check your self-hosted version (Admin > Stats or the install compose file) against the 26.4.2 floor. Upgrade self-hosted to the latest release (the docs recommend latest, not just the floor).
Steps
- You upgraded
@sentry/nodeor@sentry/browserto 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. - v11 changed the wire format: span streaming sends spans in batches as they finish instead of one transaction payload at the end,
sendDefaultPiibecamedataCollectionwith new categories, and attributes replaced tags on spans. An old server does not understand the new shapes. - 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.
- 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.
- 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=1in your self-hosted.env(available since 24.10.0) and configure the loader URL, or ship the npm bundle instead of the loader.
When to use
You are seeing this: Symptoms are vague: traces incomplete, new span fields missing, odd ingestion errors. Use this skill when you run into "Sentry: v11 SDK against old self-hosted silently misbehaves".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: 26.4.2, 24.10.0. If you are on something much newer or older, the details may have shifted.
Why this happens
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.
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 2 · 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>