feat(Sentry Dashboards): Insights EOL

.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
 

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/), [Insights](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.
 

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 our [Insights](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.

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
 

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. [Insights](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. [Insights](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/)
 

docs/concepts/key-terms/key-terms.mdx

@@ -58,7 +58,7 @@ Each of these key features have their own page (or set of pages) in the [sentry.
 
 - **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/).
+- **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/dashboards/sentry-dashboards/).
 
 - **Alerts** - Where you can create new alert rules and manage existing ones. Learn more in the full [Alerts documentation](/product/alerts/).
 

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.

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 [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/dashboards/sentry-dashboards/).
 
 ![An overview of the Performance page in Sentry.](./img/Performance-page.png)
 

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 [Metric Alerts](/product/alerts-notifications/metric-alerts/).
+`OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Sentry Dashboards](/product/dashboards/sentry-dashboards/), and [Metric Alerts](/product/alerts-notifications/metric-alerts/).
 
 </Alert>
 

docs/concepts/search/searchable-properties/events.mdx

@@ -30,7 +30,7 @@ Below is a list of keys and tokens that can be used in the event search.
 
 ### `apdex(threshold)`
 
-Returns results with the [Apdex score](/product/insights/overview/metrics/#apdex) that you entered. Values must be between `0` and `1`. Higher apdex values indicate higher user satisfaction.
+Returns results with the Apdex score that you entered. Values must be between `0` and `1`. Higher apdex values indicate higher user satisfaction.
 
 - **Type:** number
 
@@ -342,43 +342,43 @@ Returns results with a matching maximum value for the field entered.
 
 ### `measurements.app_start_cold`
 
-A [cold start](/product/insights/mobile/mobile-vitals/app-starts/) on Android refers to when the app process is created from scratch. On iOS it is only the first time a process is created after a reboot or update.
+A [cold start](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/app-starts/) on Android refers to when the app process is created from scratch. On iOS it is only the first time a process is created after a reboot or update.
 
 - **Type:** duration
 
 ### `measurements.app_start_warm`
 
-A [warm start](/product/insights/mobile/mobile-vitals/app-starts/) on Android refers to when the app launches with some saved state, for example it may have an existing process and only need to create a new Activity. On iOS it is any process creation that isn't a cold start.
+A [warm start](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/app-starts/) on Android refers to when the app launches with some saved state, for example it may have an existing process and only need to create a new Activity. On iOS it is any process creation that isn't a cold start.
 
 - **Type:** duration
 
 ### `measurements.cls`
 
-[Cumulative Layout Shift (CLS)](/product/insights/web-vitals/web-vitals-concepts/#cumulative-layout-shift-cls) is the sum of individual layout shift scores for every unexpected element shift during the rendering process.
+[Cumulative Layout Shift (CLS)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#cumulative-layout-shift-cls) is the sum of individual layout shift scores for every unexpected element shift during the rendering process.
 
 - **Type:** number
 
 ### `measurements.fcp`
 
-[First Contentful Paint (FCP)](/product/insights/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp) measures the time for the first content to render in the viewport.
+[First Contentful Paint (FCP)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp) measures the time for the first content to render in the viewport.
 
 - **Type:** duration
 
 ### `measurements.fid`
 
-[First Input Delay (FID)](/product/insights/web-vitals/web-vitals-concepts/#first-input-delay-fid) measures the response time when the user tries to interact with the viewport.
+[First Input Delay (FID)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#first-input-delay-fid) measures the response time when the user tries to interact with the viewport.
 
 - **Type:** duration
 
 ### `measurements.fp`
 
-[First Paint (FP)](/product/insights/web-vitals/web-vitals-concepts/#first-paint-fp) measures the amount of time the first pixel takes to appear in the viewport, rendering any visual change from what was previously displayed.
+[First Paint (FP)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#first-paint-fp) measures the amount of time the first pixel takes to appear in the viewport, rendering any visual change from what was previously displayed.
 
 - **Type:** duration
 
 ### `measurements.frames_frozen`
 
-[Slow and frozen frames](/product/insights/mobile/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
+[Slow and frozen frames](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
 
 - **Type:** number
 
@@ -390,7 +390,7 @@ Returns results with a matching rate of frozen frames. That is, `measurements.fr
 
 ### `measurements.frames_slow`
 
-[Slow and frozen frames](/product/insights/mobile/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
+[Slow and frozen frames](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
 
 - **Type:** number
 
@@ -408,7 +408,7 @@ Returns results with a matching total number of frames.
 
 ### `measurements.lcp`
 
-[Largest Contentful Paint (LCP)](/product/insights/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp) measures the render time for the largest content to appear in the viewport.
+[Largest Contentful Paint (LCP)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp) measures the render time for the largest content to appear in the viewport.
 
 - **Type:** duration
 
@@ -438,7 +438,7 @@ The [total stall time](/platforms/react-native/tracing/instrumentation/automatic
 
 ### `measurements.ttfb`
 
-[Time To First Byte (TTFB)](/product/insights/web-vitals/web-vitals-concepts/#time-to-first-byte-ttfb) measures the time that it takes for a user's browser to receive the first byte of page content.
+[Time To First Byte (TTFB)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#time-to-first-byte-ttfb) measures the time that it takes for a user's browser to receive the first byte of page content.
 
 - **Type:** duration
 
@@ -685,7 +685,7 @@ Span ID of the root span of the root transaction in the event.
 
 ### `transaction`
 
-For [transactions](/product/insights/overview/transaction-summary/#what-is-a-transaction), the name of the transaction. For errors, the name of the associated transaction.
+For [transactions](/product/dashboards/sentry-dashboards/transaction-summary/#what-is-a-transaction), the name of the transaction. For errors, the name of the associated transaction.
 
 - **Type:** string
 
@@ -715,7 +715,7 @@ The [Unreal Crash Context Type](https://docs.unrealengine.com/4.27/en-US/API/Run
 
 ### `user_misery(number)`
 
-Returns transactions with the defined user misery value. [User Misery](/product/insights/overview/metrics/#user-misery) is a user-weighted performance metric that counts the number of unique users who were frustrated; "frustration" is measured as a response time four times the satisfactory response time threshold (in milliseconds). It highlights transactions that have the highest impact on users.
+Returns transactions with the defined user misery value. User Misery is a user-weighted performance metric that counts the number of unique users who were frustrated; "frustration" is measured as a response time four times the satisfactory response time threshold (in milliseconds). It highlights transactions that have the highest impact on users.
 
 - **Type:** number
 

docs/concepts/search/searchable-properties/issues.mdx

@@ -426,7 +426,7 @@ A trace represents the record of the entire operation you want to measure or tra
 
 ### `transaction`
 
-For [transactions](/product/insights/overview/transaction-summary/#what-is-a-transaction), the name of the transaction. For errors, the name of the associated transaction.
+For [transactions](/product/dashboards/sentry-dashboards/transaction-summary/#what-is-a-transaction), the name of the transaction. For errors, the name of the associated transaction.
 
 - **Type:** string