sfanahata · May 7, 2026 · May 6, 2026 · May 7, 2026 · May 7, 2026 · May 7, 2026
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -27,7 +27,7 @@
 # /docs/platforms/rust/ @getsentry/team-web-sdk-backend
 
 # /docs/product/explore/discover-queries/ @getsentry/data-browsing
-# /docs/product/insights/ @getsentry/dashboards
+# /docs/product/dashboards/sentry-dashboards/ @getsentry/dashboards
 
 # /docs/cli/ @getsentry/team-web-sdk-backend
 

diff --git a/develop-docs/application-architecture/sentry-vs-getsentry.mdx b/develop-docs/application-architecture/sentry-vs-getsentry.mdx
@@ -5,7 +5,7 @@ sidebar_order: 20
 
 You'll find numerous references to both `sentry` and `getsentry` in our documentation. Both are [Django](https://www.djangoproject.com/) apps, but `sentry` [is open](https://github.com/getsentry/sentry) and `getsentry` is closed. What's in which?
 
-The main thing to emphasize is that all of our product features—[Issues](https://docs.sentry.io/product/issues/), [Insights](https://docs.sentry.io/product/insights/), [Dashboards](https://docs.sentry.io/product/dashboards/), and [such](https://docs.sentry.io/product/)—are implemented and available in `sentry`, the open component. It's really important to us that we're not an "open core" company that hides key functionality behind a paywall. [Sentry is as open-source as we can make it](https://open.sentry.io/licensing/).
+The main thing to emphasize is that all of our product features—[Issues](https://docs.sentry.io/product/issues/), [Sentry Dashboards](https://docs.sentry.io/product/dashboards/sentry-dashboards/), [Dashboards](https://docs.sentry.io/product/dashboards/), and [such](https://docs.sentry.io/product/)—are implemented and available in `sentry`, the open component. It's really important to us that we're not an "open core" company that hides key functionality behind a paywall. [Sentry is as open-source as we can make it](https://open.sentry.io/licensing/).
 
 So what's in `getsentry`, then? It implements billing and account management features for [our SaaS, sentry.io](https://sentry.io/). `getsentry` is the Django app we deploy to production. It imports the `sentry` Django app, adds some routes and models, and re-exports it.
 

diff --git a/develop-docs/backend/application-domains/transaction-clustering/index.mdx b/develop-docs/backend/application-domains/transaction-clustering/index.mdx
@@ -12,7 +12,7 @@ In terms of technical implementation, it is similar to [Data Scrubbing](/backend
 
 ## The Problem
 
-In our [Insights](https://docs.sentry.io/product/insights/overview/) product, transactions are grouped by their name
+In many of our [pre-built dashboards](https://docs.sentry.io/product/dashboards/sentry-dashboards/) product, transactions are grouped by their name
 (the [`event.transaction`](/sdk/foundations/transport/event-payloads/#optional-attributes) field).
 This works well as long as the cardinality of distinct transaction names that the SDK sends is low, for example
 by using the [route of a web framework](https://docs.sentry.io/platforms/javascript/guides/react/configuration/integrations/react-router/) as the transaction name.

diff --git a/develop-docs/sdk/getting-started/playbooks/sdk-lifecycle/breaking-changes.mdx b/develop-docs/sdk/getting-started/playbooks/sdk-lifecycle/breaking-changes.mdx
@@ -53,7 +53,7 @@ When the public/private boundary is unclear, look for evidence of external usage
 - **Grouping** — changes to event data used by the server's grouping algorithm
 - **Dashboards** — renaming or removing span attributes users may be filtering on
 - **Alerts** — attribute changes that could cause alerts to start or stop firing
-- **Insights** — changes to metrics surfaced in the Insights module (e.g., Web or Mobile Vitals)
+- **Sentry Dashboards** — changes to metrics surfaced in the dashboard widgets (e.g., Web or Mobile Vitals)
 - **Issue detection** — changes to span emission that influence server-side issue detection
 
 **Behavior changes** — changes that don't require code changes but significantly affect user experience:

diff --git a/develop-docs/sdk/telemetry/traces/modules/ai-agents.mdx b/develop-docs/sdk/telemetry/traces/modules/ai-agents.mdx
@@ -6,7 +6,7 @@ The AI Agents module is agnostic to the library used. The SDK will instrument ex
 
 ## Spans Conventions
 
-For your AI agents data to show up in the Sentry [AI Agents Insights](https://sentry.io/orgredirect/organizations/:orgslug/insights/ai/agents/), at least one of the AI spans needs to be created and have well-defined names and data attributes. If the required data (marked with MUST or required) is missing, the data will not show up in the Agents dashbboard.
+For your AI agents data to show up in the Sentry [AI Agents dashboard](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/), at least one of the AI spans needs to be created and have well-defined names and data attributes. If the required data (marked with MUST or required) is missing, the data will not show up in the Agents dashbboard.
 
 We try to follow [v1.36.0](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md) of the [OpenTelemetry Semantic Conventions](https://opentelemetry.io/docs/specs/semconv/gen-ai/) for Generative AI as close as possible. Being 100% compatible is not yet possible, because OpenTelemetry has "Span Events" which Sentry does not support. The input from/output to an AI model is stored in span events in OpenTelemetry. Since this is not possible in Sentry, we add this data onto span attributes as a list.
 

diff --git a/develop-docs/sdk/telemetry/traces/modules/index.mdx b/develop-docs/sdk/telemetry/traces/modules/index.mdx
@@ -1,7 +1,7 @@
 ---
-title: Insights Modules
+title: Dashboard Widgets
 ---
 
-The list below contains SDK documentation for our various Insights Modules (formerly known as "Performance Modules").
+The list below contains SDK documentation for our various Dashboard Modules (formerly known as "Performance Widgets").
 
 <PageGrid />
diff --git a/develop-docs/sdk/telemetry/traces/opentelemetry.mdx b/develop-docs/sdk/telemetry/traces/opentelemetry.mdx
@@ -10,7 +10,7 @@ This page is under active development. Specifications are not final and subject
 
 </Alert>
 
-This document details Sentry's work in integrating and supporting [OpenTelemetry](https://opentelemetry.io/), the open standard for metrics, traces and logs. In particular, it focuses on the integration between [Sentry's performance monitoring product](https://docs.sentry.io/product/insights/overview/) and [OpenTelemetry's tracing spec](https://opentelemetry.io/docs/concepts/signals/traces/).
+This document details Sentry's work in integrating and supporting [OpenTelemetry](https://opentelemetry.io/), the open standard for metrics, traces and logs. In particular, it focuses on the integration between [Sentry's performance monitoring product](https://docs.sentry.io/product/dashboards/sentry-dashboards/) and [OpenTelemetry's tracing spec](https://opentelemetry.io/docs/concepts/signals/traces/).
 
 ## Background
 

diff --git a/develop-docs/self-hosted/optional-features/errors-only.mdx b/develop-docs/self-hosted/optional-features/errors-only.mdx
@@ -24,9 +24,9 @@ This is our default version of self-hosted Sentry. It includes most of the featu
 1. [Traces](https://docs.sentry.io/product/explore/traces/)
 2. [Profiles](https://docs.sentry.io/product/explore/profiling/)
 3. [Replays](https://docs.sentry.io/product/explore/session-replay/)
-4. [Insights](https://docs.sentry.io/product/insights/) (Requests, Queries, Assets, etc)
+4. [Sentry Dashboards](https://docs.sentry.io/product/dashboards/sentry-dashboards/) (Requests, Queries, Assets, etc)
 5. [User Feedback](https://docs.sentry.io/product/user-feedback/)
-6. [Insights](https://docs.sentry.io/product/insights/)
+6. [Sentry Dashboards](https://docs.sentry.io/product/dashboards/sentry-dashboards/)
 7. [Crons](https://docs.sentry.io/product/monitors-and-alerts/monitors/crons/)
 8. [Application Metrics](https://docs.sentry.io/product/explore/metrics/)
 

diff --git a/docs/concepts/key-terms/key-terms.mdx b/docs/concepts/key-terms/key-terms.mdx
@@ -56,9 +56,7 @@ Each of these key features have their own page (or set of pages) in the [sentry.
 
 - **Explore** - Sentry offers multiple ways to search and investigate your application's data — including your app's traces, metrics, profiles, replays, and events — to get the information you need to debug issues more quickly and easily. Use the Discover page to query events across environments, visualize the results, and unlock insights into the health of your entire system. Learn more in the full [Explore documentation](/product/explore/).
 
-- **Insights** - Sentry surfaces insights that can help you identify opportunities at the service-level to improve various parts of your app's performance, including requests, assets, caches, queues, and more. Modules living under the Insights heading provide an overview of how your project is performing in that category, as well as the ability to review sample events and their traces to help you diagnose potential problems.
-
-- **Insights Overview** - The main view in [sentry.io](http://sentry.io) where you can search or browse for transaction data. The page displays graphs that visualize transactions or trends, as well as a table where you can view relevant transactions and drill down to more information about them. Learn more in the full [performance monitoring documentation](/product/insights/overview/).
+- **Pre-built Sentry Dashboards** - Sentry surfaces insights that can help you identify opportunities at the service-level to improve various parts of your app's performance, including requests, assets, caches, queues, and more. Pre-built Sentry Dashboards living under the Dashboards heading provide an overview of how your project is performing in various categories, as well as the ability to review sample events and their traces to help you diagnose potential problems. Learn more in the full [Sentry Dashboards documentation](/product/dashboards/sentry-dashboards/).
 
 - **Alerts** - Where you can create new alert rules and manage existing ones. Learn more in the full [Alerts documentation](/product/monitors-and-alerts/alerts/).
 

diff --git a/docs/concepts/key-terms/tracing/distributed-tracing.mdx b/docs/concepts/key-terms/tracing/distributed-tracing.mdx
@@ -8,7 +8,7 @@ description: >-
 og_image: /og-images/concepts-key-terms-tracing-distributed-tracing.png
 ---
 
-Distributed tracing provides a connected view of your application from frontend to backend. It helps track software performance, measure [metrics](/product/dashboards/sentry-dashboards/transaction-summary/#metrics-in-this-view) like throughput and latency, and display the impact of errors across multiple systems. This makes Sentry a more complete [performance monitoring](/product/insights/overview/) solution, aiding in diagnosing problems and measuring your application's overall health.
+Distributed tracing provides a connected view of your application from frontend to backend. It helps track software performance, measure [metrics](/product/dashboards/sentry-dashboards/transaction-summary/#metrics-in-this-view) like throughput and latency, and display the impact of errors across multiple systems. This makes Sentry a more complete [performance monitoring](/product/dashboards/sentry-dashboards/) solution, aiding in diagnosing problems and measuring your application's overall health.
 
 [Tracing](/concepts/key-terms/tracing/distributed-tracing/) in Sentry provides insights such as:
 
@@ -80,7 +80,7 @@ Distributed tracing allows you to follow a request from the [frontend](/product/
 
 A **trace** represents the record of the entire operation you want to measure or track, like page load or a user action. When a trace includes work in multiple services, it's called a **distributed trace**.
 
-Each trace consists of one or more tree-like structures called [**transactions**](/product/insights/overview/transaction-summary/), with nodes called **spans**. Each transaction represents a single instance of a service being called, and each span represents a single unit of work. Here's an example trace, broken down into transactions and spans:
+Each trace consists of one or more tree-like structures called [**transactions**](/product/dashboards/sentry-dashboards/transaction-summary/), with nodes called **spans**. Each transaction represents a single instance of a service being called, and each span represents a single unit of work. Here's an example trace, broken down into transactions and spans:
 
 ![Diagram illustrating how a trace is composed of multiple transactions, and each transaction is composed of multiple spans.](./img/diagram-transaction-trace.png)
 
@@ -231,4 +231,4 @@ Dynamic sampling ensures complete traces by retaining all transactions associate
 
 Use the [Trace Explorer](/product/explore/traces/) to search for traces containing spans that meet your specific query conditions. This helps you find distributed traces that give you a connected view of your application and can help you debug and optimize your code.
 
-Through [Performance](/product/insights/overview/) and [Discover](/product/explore/discover-queries/), you can also view trace data in the [Trace View](/concepts/key-terms/tracing/trace-view/) page.
+Through [Performance](/product/dashboards/sentry-dashboards/) and [Discover](/product/explore/discover-queries/), you can also view trace data in the [Trace View](/concepts/key-terms/tracing/trace-view/) page.
diff --git a/docs/concepts/key-terms/tracing/index.mdx b/docs/concepts/key-terms/tracing/index.mdx
@@ -17,7 +17,7 @@ Tracing involves capturing the timing and flow of requests and operations as the
 
 Distributed tracing provides a unified view of how a single request moves from the frontend to the backend and beyond. This is particularly useful in modern applications, which are often composed of multiple separate services working together. To get a distributed view of your application, instrument Sentry in both your frontend and your backend.
 
-With [distributed tracing](/concepts/key-terms/tracing/distributed-tracing/), you can identify performance bottlenecks that are affecting your application across different services and platforms. You can then use Sentry tools such as the [Trace Explorer](/product/explore/traces/) or [Trace View](/concepts/key-terms/tracing/trace-view/) page to dig deeper and find the root cause of the problem. Distributed tracing is particularly helpful for identifying problems that take place between multiple services that you can't debug using console logs, such as race conditions, [N+1 queries](/product/issues/issue-details/performance-issues/n-one-queries/), and [caching issues](/product/insights/caches/).
+With [distributed tracing](/concepts/key-terms/tracing/distributed-tracing/), you can identify performance bottlenecks that are affecting your application across different services and platforms. You can then use Sentry tools such as the [Trace Explorer](/product/explore/traces/) or [Trace View](/concepts/key-terms/tracing/trace-view/) page to dig deeper and find the root cause of the problem. Distributed tracing is particularly helpful for identifying problems that take place between multiple services that you can't debug using console logs, such as race conditions, [N+1 queries](/product/issues/issue-details/performance-issues/n-one-queries/), and [caching issues](/product/dashboards/sentry-dashboards/backend/caches/).
 
 ### What's a Trace?
 
@@ -55,7 +55,7 @@ Alternatively, you can use the search bar to look for spans by name, project, or
 
 ### Performance to Trace View
 
-Depending on the size and volume of your app, you may have a lot of traces to sort through. The [Insights](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/) page in Sentry is a good place to get a high-level, aggregated view of your application's performance and focus in on the traces you care about. You'll see a list of transactions for specific pages, endpoints and parts of your application. Clicking on the transaction ID will take you to the Trace View page for that transaction. Learn more about using Sentry's [Insights](/product/insights/).
+Depending on the size and volume of your app, you may have a lot of traces to sort through. The [Sentry Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/) page in Sentry is a good place to get a high-level, aggregated view of your application's performance and focus in on the traces you care about. You'll see a list of transactions for specific pages, endpoints and parts of your application. Clicking on the transaction ID will take you to the Trace View page for that transaction. Learn more about using [Sentry Dashboards](/product/dashboards/sentry-dashboards/).
 
 ![An overview of the Performance page in Sentry.](./img/Performance-page.png)
 

diff --git a/docs/concepts/search/index.mdx b/docs/concepts/search/index.mdx
@@ -60,7 +60,7 @@ Here are some examples of valid comparison operator searches:
 
 <Alert>
 
-`OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Insights Overview](/product/insights/overview/), and [Monitors](/product/monitors-and-alerts/monitors/).
+`OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Sentry Dashboards](/product/dashboards/sentry-dashboards/), and [Monitors](/product/monitors-and-alerts/monitors/).
 
 </Alert>
 
@@ -148,7 +148,7 @@ Page filters allow you to narrow down the results shown on a page by selecting s
 ### Dashboard Page Filters
 Dashboard page filters allow you to narrow down the widget results to certain projects, environments, date ranges, and releases. You can also add custom filters to your dashboard by pressing the _plus_ button. Each filter begins with selecting a dataset, and then adding a filter condition.
 
-### Insights Page Filters
+### Sentry Dashboards Page Filters
 
 ![Project selector](./img/project-selector.png)