docs(javascript): Prepare JavaScript SDK v11 documentation - #19557
Merged
Merged
Conversation
) Update JavaScript tracing docs and examples to use v11 span attributes, including HTTP, database, Gen AI, and the root-span source constant. Explain low-cardinality span names as the default behavior. Clarify that `useOperationNameForRootSpan` controls `sentry.graphql.operation` on the enclosing root span in both modes, but only renames it in static mode. The GraphQL span's own operation attributes are recorded regardless of the option. Fixes https://linear.app/getsentry/issue/SDK-1475 ## IS YOUR CHANGE URGENT? - [x] No deadline: Not urgent, can wait up to 1 week+
The Ember setup guide now initializes Sentry in `app/app.ts` and enables tracing through an instance initializer. It also calls `loadInitializers()` so Ember loads that initializer. The options page documents performance settings on `instrumentAppInstancePerformance()`, including component and runloop thresholds, instead of the old addon config. Verified against the v10-to-v11 migration guide and Ember SDK implementation. Fixes [SDK-1484](https://linear.app/getsentry/issue/SDK-1484/rewrite-ember-setup-for-the-v2-embroider-addon-in-docs). ## IS YOUR CHANGE URGENT? - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+
## DESCRIBE YOUR PR Make streamed spans the default in the JavaScript tracing callback and helper docs. Keep transaction APIs documented for static mode, with separate examples for both modes. Update filtering, naming, sensitive-data scrubbing, and MCP guidance to use the appropriate callbacks. Closes [SDK-1473](https://linear.app/getsentry/issue/SDK-1473/update-span-streaming-callbackhelper-docs). ## IS YOUR CHANGE URGENT? - [x] No deadline: Not urgent, can wait up to 1 week+
<!-- Keep the urgency section so automation can prioritize this PR. You may delete other sections you don't need. --> ## DESCRIBE YOUR PR Update the JavaScript browser docs for SDK v11’s session defaults and tracing integrations. Document page-based sessions, the unhandled session status, and the FetchStreamPerformance, Interactions, UserTiming, and WebVitals integrations. Align the migration guide, interactive migration snippets, Next.js tracing guide, and Web Vitals documentation with these behaviors. Closes SDK-1478 Closes SDK-1479 ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+
) Document v11 OpenTelemetry support with two setup guides: capture OpenTelemetry API spans through Sentry, or connect an existing OpenTelemetry pipeline to Sentry. The OpenTelemetry Support landing page uses a PageGrid to explain when to choose each setup, its configuration, and how spans reach Sentry. Default Sentry tracing links to the existing tracing docs. Add a separate integration reference for `openTelemetryIntegration()` and `getOtlpTracesEndpoint()`. Preserve the v10 overview, two subpages, and setup examples as versioned docs, with links and snippet references that keep readers on v10. The current setup guides retain their existing URLs. Update HTTP and fetch propagation guidance for the separate tracing pipelines, and remove obsolete ESM loader troubleshooting from the installation guides. Fixes https://linear.app/getsentry/issue/SDK-1470 Fixes https://linear.app/getsentry/issue/SDK-1471 Fixes https://linear.app/getsentry/issue/SDK-1490 ## IS YOUR CHANGE URGENT? - [x] No deadline: Not urgent, can wait up to 1 week+
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
## DESCRIBE YOUR PR closes SDK-1494 (kept the version v18 ranges as they ill be removed here: #19317) Bring the Node install pages in line with the v11 install methods, and fix the ESM snippets that stop the app from starting. - Fix the extensionless `import "./instrument"` in the Express, Fastify, Hapi and Connect ESM tabs, in `install/esm-without-import.mdx` and in the NestJS ESM page. The config step creates `instrument.mjs`, and Node ESM does not probe extensions, so the app stopped with `ERR_MODULE_NOT_FOUND`. - Start the Koa ESM tab with `--import` instead. With the extension fixed the app starts, but `koa` is already loaded when `Sentry.init` runs, so every router and middleware span and every route name is lost. - Rewrite `install/late-initialization.mdx` around `node --import @sentry/node/import`. The page told readers to use `@sentry/node/preload`, which is no longer exported and fails with `ERR_PACKAGE_PATH_NOT_EXPORTED`. Drop `SENTRY_PRELOAD_INTEGRATIONS` with it, and show a CommonJS entry point next to the ESM one, since `--import` covers both. - Rework `install/index.mdx` around the three v11 methods: `--import` your instrument file, a bundler plugin with a top-level import, and `--import` the SDK with a later `Sentry.init()`. Say that `--import` covers CommonJS as well, and that `--require` is gone. - Rewrite `install/esm-without-import.mdx` around the bundler plugin and the deferred entry point, and say why a top-level import alone is not equivalent to `--import`. - Remove the `registerEsmLoaderHooks` troubleshooting from `install/esm.mdx`. The option was removed and the SDK no longer depends on `import-in-the-middle`. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
## DESCRIBE YOUR PR closes SDK-1485 `sentrySvelteKit` no longer lives on the `@sentry/sveltekit` entry, so every snippet that imported it from there fails the build with `SyntaxError: The requested module '@sentry/sveltekit/build/esm/index.server.js' does not provide an export named 'sentrySvelteKit'`. The plugin is exported only from `@sentry/sveltekit/vite`. Update all thirteen snippets on the current pages: - the three `vite.config` snippets in the getting-started include - the four in the source maps overview - the three in the source maps primer - the three on the build configuration page Also update the primer for the removed `sourceMapsUploadOptions`: its fields sit at the top level of the plugin options now, which the snippet already showed but the prose did not, and `url` became `sentryUrl`. The v8 and v10.7.0 manual setup pages keep the old import, since it was correct on those versions, and the migration entries keep it as their "Before" example. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
## DESCRIBE YOUR PR closes SDK-1495 Ten stream mode includes presented stream as opt-in and called `'static'` "(the default)". v11 inverts that: `packages/core/src/client.ts` normalizes with `options.traceLifecycle === 'static' ? 'static' : 'stream'`, so every value except an explicit `'static'` resolves to stream, and the migration guide calls stream mode "the new default". The page's prerequisites allow SDK `>=10.66.0`, where stream mode is real but opt-in, so keep the snippet and name the version it applies to: enabled by default in v11, set explicitly on older versions. Drop "(the default)" from the transaction mode line, and say that mode exists for backwards compatibility. Also add the missing comma after `tracesSampleRate: 0.2` in the Cloudflare Pages snippet, which did not parse. The browser and meta-framework client sections are untouched. Those enable stream mode with `spanStreamingIntegration()`, which is opt-in on every version. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
…r v11 (#19547) ## DESCRIBE YOUR PR For JS SDK v11, all gen-AI provider packages are auto-instrumented, so their Agent Tracing setup pages become standard integration reference pages, and the Agent Tracing page becomes a summary of what Sentry supports. - Moved `openai`, `anthropic`, `google-genai`, `langchain`, `langgraph`, and `vercelai` from `agent-tracing/*` sub-pages into `configuration/integrations/*`, rewritten as auto-enabled integrations (import name, how to add, options) with a "requires SDK v11+" note and `supportedCategories: [server, serverless]` - Added new integration pages: **Mistral AI**, **Groq**, **Together AI** (sourced from the SDK `server-utils` integrations) - Rewrote the Agent Tracing index: moved the instrumentation grid to the top, dropped "Getting Started" (now just "works out of the box"), completed the provider list; kept Tracking Conversations / Options / Manual Instrumentation / MCP. `flue` and `manual-instrumentation` remain as sub-pages - Repointed and extended the 14 per-platform integration tables (added langgraph/mistral/groq/together rows) - Reversed the old `integrations → agent-tracing` redirects and added `agent-tracing → integrations` redirects - Wired `mistral`/`groq` platform icons; removed Mastra/Eve from the Agent Tracing sidebar - Updated cross-references (product/agents, concepts, flue, nodejs-compat, manual-instrumentation include) Validation: `lint:ts`, `eslint`, `lint:redirect-chains` (no chains, no content links to redirect sources), and `prettier` all pass. > Note: `/brand-guidelines` and the `docs-review` skill were not run (managed skills aren't installed in this environment) — worth a pass before merge. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
## DESCRIBE YOUR PR Updates the React Router Framework docs for SDK v11: state the new 7.15 framework-mode minimum, drop the beta warnings, only describe the instrumentation API for server-side tracing, and fix the snippets that no longer build against v11. - Change the stated support in the page descriptions from "v7+" to "v7.15+" - Add a `getting-started-prerequisites` include for React Router that lists the `7.15.0` minimum (framework mode) - Drop the feature-scoped "React Router 7.15+" notes around the `instrumentations` export, since 7.15 is now the baseline - Remove the "This SDK is currently in beta" alerts from the getting started and manual setup pages - Import `sentryReactRouter`, `SentryReactRouterBuildOptions`, and `sentryOnBuildEnd` from `@sentry/react-router/vite` on the manual setup and Hydrogen pages - Fix the `entry.server.tsx` snippet to import `../instrument.server` (the file lives in the project root, the entry in `app/`) - Move the misplaced `+` diff marker in the `react-router.config.ts` snippet so it no longer renders as a unary plus The removed `wrapServerLoader` / `wrapServerAction` wrappers are already covered by the v10-to-v11 migration guide and aren't referenced anywhere else in the docs. Supersedes #19314. > **⚠️ Do not merge until v11 is released as stable.** Fixes https://linear.app/getsentry/issue/SDK-1466/update-react-router-minimum-version-to-715-in-docs Fixes https://linear.app/getsentry/issue/SDK-1486/update-react-router-vite-plugin-imports-for-v11-in-docs Fixes https://linear.app/getsentry/issue/SDK-1516/react-router-getting-started-manual-setup ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01833WEY4kqAQNfbtu9Z8JLr --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Removes `enableMetrics` from the JS metrics docs and documents the `*.logs.metrics` CDN bundle requirement for v11. Closes https://linear.app/getsentry/issue/SDK-1477/update-metrics-docs-for-v11
Rewrites the Fastify error handler page for v11. `setupFastifyErrorHandler` is a deprecated no-op in v11, so the page now documents only the happy path: errors are captured by `fastifyIntegration`, which is enabled by default, and `shouldHandleError` is configured on the integration. This also removes the old snippet's import of `@sentry/fastify`, a package that does not exist. Closes https://linear.app/getsentry/issue/SDK-1496/fastify-getting-started-manual-setup --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
…#19425) Fixes the Remix manual setup and the Remix on Cloudflare page for v11. The handleError and Vite snippets no longer break the build, the Cloudflare branch now documents a working Workers setup (`withSentry` + `instrumentBuild`, `handleError` from `@sentry/remix/cloudflare`, `sentryCloudflareVitePlugin`), and v10-only bits like `--require` are gone. It also updates the Cloudflare Vite plugin page to the shipped top-level `buildTimeInstrumentation` and `autoInstrumentation` options, and adds a request isolation warning for `wrapRequestHandler` to both Hydrogen pages. Closes https://linear.app/getsentry/issue/SDK-1512/remix-getting-started-manual-setup
…9427) The legacy `profilesSampleRate`/`profilesSampler` options were removed in favor of session-based profiling. This updates the Firebase and Hono guides to use `profileSessionSampleRate` with `profileLifecycle: "trace"` (Firebase was also missing `nodeProfilingIntegration()`), and removes the deprecated `profilesSampleRate` entries from the JavaScript options reference. Closes https://linear.app/getsentry/issue/SDK-1489/fix-remaining-legacy-profiling-options-in-docs
## DESCRIBE YOUR PR Set the Astro minimum to 4.0.0 for v11 and drop the now-moot `3.5.2` version qualifiers from the server-instrumentation notes. > **⚠️ Do not merge until v11 is released as stable.** ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: Andrei Borza <andrei.borza@sentry.io>
…ans (#19549) ## DESCRIBE YOUR PR With span streaming enabled, spans only carry attributes, so scope tags and extra (`setTag`, `setTags`, `setExtra`, `setExtras`) no longer reach any span. They still apply to errors, and in transaction mode (`traceLifecycle: "static"`) they keep landing on the transaction. This adds a note about that to the three JavaScript enriching-events pages where readers set that data, and points them to `setAttribute`/`setAttributes` for anything that should be searchable on spans. - `enriching-events/tags/` — extend the existing "not applied to logs or metrics" warning to cover spans - `enriching-events/scopes/` — callout after the "How Scope Data is Applied to Events" example - `enriching-events/attributes/` — callout in the intro, noting attributes keep their type Refs SDK-1474 --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
## DESCRIBE YOUR PR Set the Node.js minimum to 20.19.0 for v11 across the docs: reword the prerequisites with the full supported range, drop the now-moot "only available for Node v18.19.0 onwards" ESM notes (the minimum already guarantees them), and bump the stale Node-18 minimums on the Nitro and Elysia guides. > **⚠️ Do not merge until v11 is released as stable.** ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Renames the JS `InboundFilters` integration page to `EventFilters` for v11, adds redirects from the old URLs, and updates the integration tables and examples. Closes https://linear.app/getsentry/issue/SDK-1481/rename-the-inboundfilters-integration-to-eventfilters-in-docs
## DESCRIBE YOUR PR Docs still described `httpIntegration` options that v11 renamed or removed. - Rename: `trackIncomingRequestsAsSessions` → `sessions`, `maxIncomingRequestBodySize` → `maxRequestBodySize`, `ignoreIncomingRequestBody` → `ignoreRequestBody`, `dropSpansForIncomingRequestStatusCodes` → `ignoreStatusCodes`, `incomingRequestSpanHook` → `onSpanCreated` - Flag `ignoreStatusCodes` as deprecated and `traceLifecycle: 'static'` only - Replace the removed `instrumentation` hooks with `onSpanCreated` / `outgoingRequestHook`, and document the two other outgoing hooks - Fix three pre-existing errors found while verifying against the SDK source: the `spans` default, `ignoreOutgoingRequests` trace headers, and the intro Fixes SDK-1476 --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Member
|
|
…19475) ## DESCRIBE YOUR PR In SDK v11, Vercel AI instrumentation relies on diagnostics channels, which the Edge runtime doesn't support. `@sentry/nextjs` keeps `vercelAIIntegration` on its Edge build as a no-op shim so imports still resolve, but it captures nothing. The Vercel AI page still told Next.js users to add the integration to `sentry.edge.config`, which would silently produce no spans. - Replace the Node vs. Edge runtime table with a note that only the Node runtime is instrumented, linking to the migration guide - Remove the Edge setup snippet and Edge-specific caveats (`recordInputs`/`recordOutputs`, options, `force`, "both runtimes" wording) - Mark the Edge runtime as unsupported in SDK `11.0.0`+ under Supported Versions Refs SDK-1483 Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
# Conflicts: # docs/platforms/javascript/common/agent-tracing/anthropic.mdx # docs/platforms/javascript/common/agent-tracing/google-genai.mdx # docs/platforms/javascript/common/agent-tracing/index.mdx # docs/platforms/javascript/common/agent-tracing/langchain.mdx # docs/platforms/javascript/common/agent-tracing/langgraph.mdx # docs/platforms/javascript/common/agent-tracing/manual-instrumentation.mdx # docs/platforms/javascript/common/agent-tracing/openai.mdx # docs/platforms/javascript/common/agent-tracing/vercelai.mdx # docs/platforms/javascript/common/configuration/integrations/console.mdx # docs/platforms/javascript/common/configuration/integrations/modules.mdx # docs/platforms/javascript/common/configuration/integrations/onuncaughtexception.mdx # docs/platforms/javascript/common/configuration/integrations/requestdata.mdx # docs/platforms/javascript/common/configuration/integrations/supabase.mdx # docs/platforms/javascript/common/configuration/integrations/trpc.mdx # docs/platforms/javascript/common/configuration/integrations/unhandledrejection.mdx # docs/platforms/javascript/guides/nestjs/install/esm.mdx # platform-includes/getting-started-use/javascript.koa.mdx
andreiborza
marked this pull request as ready for review
September 23, 2026 10:58
andreiborza
requested review from
JPeer264,
Lms24,
chargome,
isaacs,
logaretm,
msonnb,
mydea,
nicohrubec and
s1gr1d
and removed request for
a team
September 23, 2026 10:59
nicohrubec
approved these changes
Sep 23, 2026
Improvements for `dataCollection` snippets so they are aligned everywhere. Especially for genAI snippets and versioned docs (v10). Reference (regarding MCP): getsentry/sentry-javascript#24604
## DESCRIBE YOUR PR Bring the static and interactive v11 migration guides in line with the latest [JavaScript SDK migration notes](https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md). Both guides now cover the missing span names and attributes, Web Vitals changes, AI span removals, Next.js tunnel middleware behavior, Remix source-map uploads, and webpack plugin requirements. The interactive guide adds dedicated items for Next.js tunnel requests, the webpack import change, and removed non-inference AI spans. Existing tracing items carry the corresponding naming and attribute updates so both guides give the same migration guidance. ## IS YOUR CHANGE URGENT? - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+
msonnb
approved these changes
Sep 23, 2026
## DESCRIBE YOUR PR `instrumentD1WithSentry` was removed in v11, and `withSentry()` instruments D1 and other bindings on env automatically. Remove the D1 page and add a Bindings page that lists which bindings the SDK instruments and what each one captures. Redirect the old D1 URL to the new page and link to it from the v11 migration entry. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
JPeer264
approved these changes
Sep 23, 2026
andreiborza
added a commit
to getsentry/sentry
that referenced
this pull request
Sep 23, 2026
Collects the JavaScript SDK v11 onboarding changes merged into `js-v11-onboarding` for release to `master`. The individual onboarding PRs target this branch so the updates can ship together. Keep this PR in draft with the `Do Not Merge` label until the JavaScript SDK v11 release is ready. Related documentation release PR: getsentry/sentry-docs#19557 --------- Co-authored-by: Martin Sonnberger <martin.sonnberger@sentry.io> Co-authored-by: Jan Peer Stöcklmair <jan.peer@sentry.io> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: isaacs <i@izs.me> Co-authored-by: Charly Gomez <charly.gomez@sentry.io> Co-authored-by: Codex <noreply@openai.com> Co-authored-by: Sigrid <32902192+s1gr1d@users.noreply.github.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
Related to SDK-1296.
Collects the JavaScript SDK v11 documentation changes merged into
js-v11-docsfor release tomaster. The individual documentation PRs target this branch so the updates can ship together.Keep this PR in draft with the
Do not mergelabel until the JavaScript SDK v11 release is ready.IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST