getsentry · coolguyzone · Sep 25, 2026
diff --git a/docs/concepts/key-terms/sample-rates.mdx b/docs/concepts/key-terms/sample-rates.mdx
@@ -37,7 +37,7 @@ Some of the options below aren't available in every SDK; check out our platform-
 
 - **tracesSampler** - A function responsible for determining the percentage chance a given transaction will be sent to Sentry. It will automatically be passed information about the transaction and the context in which it's being created, and must return a number between 0 (0% chance of being sent) and 1 (100% chance of being sent). Can also be used for filtering transactions, by returning 0 for those that are unwanted. Either this or `tracesSampleRate` must be defined to enable tracing.
 
-Learn more about [tracing](/product/tracing/) in Sentry.
+Learn more about [tracing](/concepts/key-terms/tracing/) in Sentry.
 ### Session Replay
 
 - **replaysSessionSampleRate** - The sample rate for replays that begin recording immediately and last the entirety of the user's session. 1.0 collects all replays, and 0 collects none.

diff --git a/docs/platforms/javascript/common/session-replay/index.mdx b/docs/platforms/javascript/common/session-replay/index.mdx
@@ -14,7 +14,7 @@ description: "Learn how to enable Session Replay in your app if it is not alread
 <PlatformSection supported={["javascript.capacitor"]}>
   <Alert level="warning" title="Not Supported on Capacitor">
 
-Session Replay is no longer supported in `@sentry/capacitor` as of version 4.0.0. If you need Session Replay, we recommend [`@sentry/react-native`](/platforms/react-native/) or [`sentry-dart` (Flutter)](/platforms/flutter/).
+Session Replay is no longer supported in `@sentry/capacitor` as of version 4.0.0. If you need Session Replay, we recommend [`@sentry/react-native`](/platforms/react-native/) or [`sentry-dart` (Flutter)](/platforms/dart/guides/flutter/).
 
 </Alert>
 </PlatformSection>

diff --git a/docs/platforms/javascript/guides/capacitor/migration/v3-to-v4/index.mdx b/docs/platforms/javascript/guides/capacitor/migration/v3-to-v4/index.mdx
@@ -19,14 +19,14 @@ All other features continue to be supported, including error and crash reporting
 
 Capacitor's WebView-based architecture creates unique challenges for features like Session Replay that need to bridge the native and web layers. Rather than ship a subpar experience, we're focusing on making error monitoring rock-solid.
 
-Additionally, Sentry is investing heavily in [`@sentry/react-native`](/platforms/react-native/) and [`sentry-dart`](/platforms/flutter/) as primary cross-platform mobile SDKs. Both support the full Sentry feature set including Session Replay, Profiling, and Performance Monitoring.
+Additionally, Sentry is investing heavily in [`@sentry/react-native`](/platforms/react-native/) and [`sentry-dart`](/platforms/dart/guides/flutter/) as primary cross-platform mobile SDKs. Both support the full Sentry feature set including Session Replay, Profiling, and Performance Monitoring.
 
 ## Migration Path
 
 If you need Session Replay or Profiling in your Capacitor app, consider migrating to one of our full-featured cross-platform SDKs. Both React Native and Flutter receive full support for all Sentry features:
 
 - **[React Native](/platforms/react-native/)**
-- **[Flutter](/platforms/flutter/)**
+- **[Flutter](/platforms/dart/guides/flutter/)**
 
 By migrating to either platform, you'll gain access to Session Replay, Profiling, Performance Monitoring, and all other Sentry features with native integration.
 

diff --git a/docs/platforms/javascript/guides/cordova/index.mdx b/docs/platforms/javascript/guides/cordova/index.mdx
@@ -12,7 +12,7 @@ categories:
 
 Cordova is being superseded by modern alternatives like [Capacitor](https://ionic.io/resources/articles/capacitor-vs-cordova-modern-hybrid-app-development).
 This SDK is no longer maintained by Sentry. If you are starting a new project or planning a [migration](https://capacitorjs.com/docs/cordova/migration-strategy), consider
-using [Sentry Capacitor](/platforms/javascript/guides/capacitor/), [Sentry React Native](/platforms/react-native/), or [Sentry Flutter](/platforms/flutter/) instead.
+using [Sentry Capacitor](/platforms/javascript/guides/capacitor/), [Sentry React Native](/platforms/react-native/), or [Sentry Flutter](/platforms/dart/guides/flutter/) instead.
 
 </Alert>
 

diff --git a/docs/platforms/javascript/guides/react/features/component-names.mdx b/docs/platforms/javascript/guides/react/features/component-names.mdx
@@ -79,7 +79,7 @@ To avoid these errors, you can exclude specific components from annotation by us
 </Alert>
 
 Now, you will be able to see your component names in breadcrumbs, spans, and search for replays by component names.
-See [this page](/product/reference/search/searchable-properties/session-replay/#clickcomponent_name) for more information on searching for Replays by component name.
+See [this page](/concepts/search/searchable-properties/session-replay/#clickcomponent_name) for more information on searching for Replays by component name.
 
 
 ### How It Works

diff --git a/docs/platforms/php/guides/laravel/tracing/distributed-tracing.mdx b/docs/platforms/php/guides/laravel/tracing/distributed-tracing.mdx
@@ -5,7 +5,7 @@ sidebar_section: features
 description: "Learn how to connect backend and frontend transactions."
 ---
 
-If you're also using Tracing for [JavaScript](/platforms/javascript/tracing/), you can use a helper function to continue the trace and propagate the trace context started from your backend in order to enable [Distributed Tracing](/platforms/javascript/tracing/trace-propagation/). (The trace context contains additional trace-related data that is used for trace-based sampling.)
+If you're also using Tracing for [JavaScript](/platforms/javascript/tracing/), you can use a helper function to continue the trace and propagate the trace context started from your backend in order to enable [Distributed Tracing](/platforms/javascript/tracing/distributed-tracing/). (The trace context contains additional trace-related data that is used for trace-based sampling.)
 Add the following line to your blade template rendering the `<head/>` of your page:
 
 ```php {filename:app.blade.php}

diff --git a/docs/platforms/unity/configuration/options/cli-options/index.mdx b/docs/platforms/unity/configuration/options/cli-options/index.mdx
@@ -5,7 +5,7 @@ sidebar_order: 30
 og_image: /og-images/platforms-unity-configuration-options-cli-options.png
 ---
 
-The Unity SDK includes [Sentry CLI](/product/cli/) as a tool to upload debug symbols to Sentry. These debug symbols are used in processing events sent to Sentry to provide stacktraces and linenumbers. This page describes the options available to configure the Sentry CLI.
+The Unity SDK includes [Sentry CLI](/cli/) as a tool to upload debug symbols to Sentry. These debug symbols are used in processing events sent to Sentry to provide stacktraces and linenumbers. This page describes the options available to configure the Sentry CLI.
 
 ## Programmatic Configuration
 

diff --git a/docs/product/agents/privacy.mdx b/docs/product/agents/privacy.mdx
@@ -38,6 +38,6 @@ However, the following agent span attributes are not protected by default:
 - `gen_ai.response.object`
 
 </Alert>
-If you wish to enable Data Scrubbing for any of these fields you can add an [Advanced Data Scrubbing](/product/data-management-settings/scrubbing/advanced-datascrubbing/) rule in [Organization-level **Security & Privacy** settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/security-and-privacy/) or [Project-level **Security & Privacy** settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/projects/:projectId/security-and-privacy/) in the following format: `$span.data.'<span attribute>'`.
+If you wish to enable Data Scrubbing for any of these fields you can add an [Advanced Data Scrubbing](/security-legal-pii/scrubbing/advanced-datascrubbing/) rule in [Organization-level **Security & Privacy** settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/security-and-privacy/) or [Project-level **Security & Privacy** settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/projects/:projectId/security-and-privacy/) in the following format: `$span.data.'<span attribute>'`.
 
 ![Additional Sensitive Fields](./img/advanced-scrubbing-rule.png)
diff --git a/docs/product/issues/issue-details/low-value-span-issues/index.mdx b/docs/product/issues/issue-details/low-value-span-issues/index.mdx
@@ -18,7 +18,7 @@ Sentry groups matching spans into a single low-value span issue. These issues ar
 
 The **Issue Details** page for a low-value span issue summarizes the offending span and its projected impact:
 
-- **Affected span** — A summary of the span Sentry detected. Click through to see matching spans in [Trace Explorer](/product/explore/trace-explorer/).
+- **Affected span** — A summary of the span Sentry detected. Click through to see matching spans in [Trace Explorer](/product/trace-explorer/).
 - **Span count** — Projected 30-day volume of this span, extrapolated from a recent sample.
 - **Estimated cost** — Projected 30-day cost of ingesting and storing this span, when available.
 - **Average duration** — Average duration of this span in the analyzed sample.

diff --git a/docs/product/monitors-and-alerts/monitors/uptime-monitoring/uptime-tracing.mdx b/docs/product/monitors-and-alerts/monitors/uptime-monitoring/uptime-tracing.mdx
@@ -5,7 +5,7 @@ description: Learn how to use distributed tracing to troubleshoot downtime.
 og_image: /og-images/product-uptime-monitoring-uptime-tracing.png
 ---
 
-Sentry's Uptime Monitoring uses [distributed tracing](/product/tracing/#whats-distributed-tracing) to track the flow and timing of requests and operations during uptime checks. This helps you quickly find the root cause of downtime by connecting related errors and performance data.
+Sentry's Uptime Monitoring uses [distributed tracing](/concepts/key-terms/tracing/#whats-distributed-tracing) to track the flow and timing of requests and operations during uptime checks. This helps you quickly find the root cause of downtime by connecting related errors and performance data.
 
 When uptime checks are performed, Sentry creates a **trace** that shows the complete request lifecycle. This trace contains:
 
@@ -19,7 +19,7 @@ When uptime checks are performed, Sentry creates a **trace** that shows the comp
 
 Sentry Uptime Tracing automatically appends a `sentry-trace` header to every outgoing request made to the configured URL in your Uptime Monitor settings. This header propagates a trace identifier.
 
-If one of Sentry's supported backend SDKs is configured for the application handling the incoming uptime check request, the trace will continue through your application. Learn more about [how distributed tracing works](/product/tracing/).
+If one of Sentry's supported backend SDKs is configured for the application handling the incoming uptime check request, the trace will continue through your application. Learn more about [how distributed tracing works](/concepts/key-terms/tracing/).
 
 Example Uptime check request:
 

diff --git a/docs/product/sentry-basics/getting-started-tutorial/generate-first-error.mdx b/docs/product/sentry-basics/getting-started-tutorial/generate-first-error.mdx
@@ -87,7 +87,7 @@ To go deeper, explore:
 
 - [Suspect commits & stack trace linking](/product/issues/suspect-commits/) — connect the [GitHub integration](/integrations/source-code-mgmt/github/) so Sentry can point to the commit that likely caused an error and link each stack frame straight to your source on GitHub.
 - [Seer](/product/ai-in-sentry/seer/) — Sentry's AI debugging agent. Connect your GitHub or GitLab repo and Seer can analyze issues, find the root cause, and even open a pull request with a fix. (Seer is a paid add-on; see [Seer pricing](/pricing/#seer-pricing).)
-- [Session Replay](/product/explore/session-replay/) — see a video-like reproduction of what the user did before the error
+- [Session Replay](/product/session-replay/) — see a video-like reproduction of what the user did before the error
 - [Alerts](/product/monitors-and-alerts/alerts/) — get notified in Slack or Discord about the issues you care about
 - [Dashboards](/product/dashboards/sentry-dashboards/) — track error and performance trends across your services
 - [Releases](/product/releases/) — monitor release health over time

diff --git a/...roduct/sentry-basics/getting-started-tutorial/initialize-sentry-sdk-backend.mdx b/...roduct/sentry-basics/getting-started-tutorial/initialize-sentry-sdk-backend.mdx
@@ -74,7 +74,7 @@ Sentry captures data by using a platform-specific SDK that you add to your app's
 
 1. Save the file.
 
-   The options set in `Sentry.init()` are called the SDK's configuration. The only required option is the DSN; the SDK supports many others, which you can read about in our [Configuration](/platforms/javascript/guides/node/configuration/) docs. The configuration above enables Sentry's error monitoring and [**Tracing**](/product/tracing/) features.
+   The options set in `Sentry.init()` are called the SDK's configuration. The only required option is the DSN; the SDK supports many others, which you can read about in our [Configuration](/platforms/javascript/guides/node/configuration/) docs. The configuration above enables Sentry's error monitoring and [**Tracing**](/concepts/key-terms/tracing/) features.
 
 1. Open your `server.js` file, import `Sentry`, and set up the error handler after all controllers and before any other error middleware. You don't import `instrument.js` here — you'll load it with Node's `--import` flag when you start the app (in the next step):
 

diff --git a/...oduct/sentry-basics/getting-started-tutorial/initialize-sentry-sdk-frontend.mdx b/...oduct/sentry-basics/getting-started-tutorial/initialize-sentry-sdk-frontend.mdx
@@ -90,7 +90,7 @@ Sentry captures data using a platform-specific SDK that you add to your app's ru
 
 The options set in `Sentry.init()` are called the SDK's configuration. The only required option is the DSN; the SDK supports many others, which you can read about in our [Configuration](/platforms/javascript/guides/react/configuration/) docs.
 
-The configuration above enables Sentry's error monitoring, [**Tracing**](/product/tracing/), and [**Session Replay**](/platforms/javascript/guides/react/session-replay/) features. The `tracePropagationTargets` option controls which URLs distributed tracing is enabled for. Since both of this tutorial's apps run on `localhost`, you're all set.
+The configuration above enables Sentry's error monitoring, [**Tracing**](/concepts/key-terms/tracing/), and [**Session Replay**](/platforms/javascript/guides/react/session-replay/) features. The `tracePropagationTargets` option controls which URLs distributed tracing is enabled for. Since both of this tutorial's apps run on `localhost`, you're all set.
 
 
 ## 3. Build and Run the Sample Application

diff --git a/docs/product/session-replay/mobile/index.mdx b/docs/product/session-replay/mobile/index.mdx
@@ -72,7 +72,7 @@ We recommend updating to the latest version, but the minimum versions supported
 
 <Include name="session-replay-for-backend-errors.mdx" />
 
-Make sure you've set up [trace propagation](/product/sentry-basics/concepts/tracing/#trace-propagation) in your backend projects. For example:
+Make sure you've set up [trace propagation](/concepts/key-terms/tracing/#trace-propagation) in your backend projects. For example:
 
 ```swift {tabTitle:Swift} {mdExpandTabs}
 import Sentry

diff --git a/docs/product/session-replay/web/index.mdx b/docs/product/session-replay/web/index.mdx
@@ -80,7 +80,7 @@ The Sentry SDK that records the replay runs on the client's browser, and it's bu
 
 <Include name="session-replay-for-backend-errors.mdx" />
 
-Make sure you've set up [trace propagation](/product/sentry-basics/concepts/tracing/#trace-propagation) in your backend projects. For example:
+Make sure you've set up [trace propagation](/concepts/key-terms/tracing/#trace-propagation) in your backend projects. For example:
 
 ```javascript
 Sentry.init({

diff --git a/docs/product/snapshots/index.mdx b/docs/product/snapshots/index.mdx
@@ -24,14 +24,14 @@ Snapshots helps you catch unintended visual changes before they reach users. Sen
 
 - **Auth token** — A Sentry auth token with `project:write` scope (personal token) or `org:ci` scope (org-level token).
 - **sentry-cli >= 3.5.0** — The `snapshots upload` command requires version 3.5.0 or later.
-- **GitHub integration** — Snapshots can be used with any VCS provider, but only Github is supported for status check integration and PR comments. Install the [Sentry GitHub App](/organization/integrations/source-code-mgmt/github/) and grant it access to your repository for PR integration.
+- **GitHub integration** — Snapshots can be used with any VCS provider, but only Github is supported for status check integration and PR comments. Install the [Sentry GitHub App](/integrations/source-code-mgmt/github/) and grant it access to your repository for PR integration.
 
 ## Recommended Platform Workflows
 
 Snapshots works for any platform with a frontend and most platforms have a number of tools to help you generate snapshots. Sentry has a recommended workflow for the following platforms:
 
 - [iOS](/platforms/apple/guides/ios/snapshots/)
 - [Android](/platforms/android/snapshots/)
-- [Flutter](/platforms/flutter/snapshots/)
+- [Flutter](/platforms/dart/guides/flutter/snapshots/)
 
 <PageGrid />
diff --git a/docs/product/snapshots/integrating-into-ci.mdx b/docs/product/snapshots/integrating-into-ci.mdx
@@ -17,7 +17,7 @@ Snapshots works by comparing a head vs. base build, similar to how code review c
 
 ### Installation
 
-1. Install the Sentry GitHub App by following the installation instructions in the [GitHub integration documentation](/organization/integrations/source-code-mgmt/github/).
+1. Install the Sentry GitHub App by following the installation instructions in the [GitHub integration documentation](/integrations/source-code-mgmt/github/).
 
    a. If you have previously installed the Sentry App, ensure you have accepted the latest permissions to receive status checks.
 

diff --git a/docs/product/trace-explorer/index.mdx b/docs/product/trace-explorer/index.mdx
@@ -19,7 +19,7 @@ The [**Trace Explorer**](https://sentry.io/orgredirect/organizations/:orgslug/tr
 - A trace represents a series of transactions or requests through a single system. This includes things like user browser sessions, HTTP requests, DB queries, middleware, caches and more.
 - It captures a series of operations (_spans_) that show how different parts of your application interacted during each transaction.
 - Each trace is identified by a **Trace ID**, which you can use to follow a request across services or projects.
-- A [distributed trace](/platforms/javascript/tracing/trace-propagation/#what-is-distributed-tracing) is made of transactions and spans that traverse multiple servers, clients, edge workers, and other parts of your system. It is assembled by passing the Trace ID through browser headers.
+- A [distributed trace](/platforms/javascript/tracing/distributed-tracing/#what-is-distributed-tracing) is made of transactions and spans that traverse multiple servers, clients, edge workers, and other parts of your system. It is assembled by passing the Trace ID through browser headers.
 
 ### Spans
 

diff --git a/includes/session-replay-for-backend-errors.mdx b/includes/session-replay-for-backend-errors.mdx
@@ -2,4 +2,4 @@
 
 Replays are integrated with Sentry's tracing data model, enabling you to see replays associated with backend errors. For these replays, you can view backend errors in the Timeline, the Breadcrumbs and Errors tabs, and other places when you go to the **Replay Details** view. You'll also see a Replays tab and replay previews in the **Issue Details** page for any backend error that has a linked replay.
 
-To see replays for backend errors, you need to have Sentry set up for both your frontend and backend, along with [distributed tracing](/product/sentry-basics/concepts/tracing/). This provides end-to-end data connectivity on your APIs, allowing Sentry to link replays to backend endpoints.
+To see replays for backend errors, you need to have Sentry set up for both your frontend and backend, along with [distributed tracing](/concepts/key-terms/tracing/). This provides end-to-end data connectivity on your APIs, allowing Sentry to link replays to backend endpoints.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -2,4 +2,4 @@

		Replays are integrated with Sentry's tracing data model, enabling you to see replays associated with backend errors. For these replays, you can view backend errors in the Timeline, the Breadcrumbs and Errors tabs, and other places when you go to the Replay Details view. You'll also see a Replays tab and replay previews in the Issue Details page for any backend error that has a linked replay.

		To see replays for backend errors, you need to have Sentry set up for both your frontend and backend, along with [distributed tracing](/product/sentry-basics/concepts/tracing/). This provides end-to-end data connectivity on your APIs, allowing Sentry to link replays to backend endpoints.
		To see replays for backend errors, you need to have Sentry set up for both your frontend and backend, along with [distributed tracing](/concepts/key-terms/tracing/). This provides end-to-end data connectivity on your APIs, allowing Sentry to link replays to backend endpoints.