feat(Discover EOL): Updating docs to remove Discover pages and add Explore > Errors

.github/CODEOWNERS

@@ -27,7 +27,7 @@
 # /docs/platforms/rust/ @getsentry/team-web-sdk-backend
 # /docs/platforms/python/ @getsentry/owners-python-sdk
 
-# /docs/product/explore/discover-queries/ @getsentry/data-browsing
+# /docs/product/errors/ @getsentry/data-browsing
 # /docs/product/dashboards/sentry-dashboards/ @getsentry/dashboards
 
 # /docs/cli/ @getsentry/team-web-sdk-backend

docs/concepts/key-terms/enrich-data/index.mdx

@@ -58,15 +58,13 @@ On the **Issues** page, custom data allows you to:
 
 Learn more in [Search](/concepts/search/).
 
-### Discover
+### Explore
 
-Discover is a powerful query engine that builds upon your data, allowing you to reveal patterns, anomalies, and deeper insights in the health of your entire system. With this in mind, the more (custom) data you add to your events, the more flexibility you'll gain in building queries that address your environments, releases, custom development, and business characteristics through _tags_, and the end-users impacted by those events.
+Explore is a powerful query engine that builds upon your data, allowing you to reveal patterns, anomalies, and deeper insights in the health of your entire system. With this in mind, the more (custom) data you bring into Sentry, the more flexibility you'll gain in building queries that address your environments, releases, custom development, and business characteristics. Sentry supports telemetry data from a wide range of sources, like [errors](/product/errors/), [traces and spans](/product/trace-explorer/), [logs](/product/logs/), [session replays](/product/session-replay/web/), and [application metrics](/product/metrics/).
 
-For instance, the Discover query below displays all the errors (total of 143 events) that occurred in the _production environment_, distributed by the _customer-type custom tag_, and ordered by the _uniquely impacted end users_.
+For instance, a Traces query can display all the spans that occurred in the _production environment_, aggregated by the _customer-type custom tag_, and ordered by _p90(span.duration)_.
 
-![Discover Query](./img/004.png)
-
-Learn more in [Discover](/product/discover-queries/).
+Learn more in [Traces and Spans](/product/trace-explorer/).
 
 ### Ownership Rules
 

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

@@ -54,7 +54,7 @@ Each of these key features have their own page (or set of pages) in the [sentry.
 
 - **Projects** - Lists the projects of which you're a member, by team, and provides you with a high-level overview of your projects. From here, you can go to the **Project Details** page of each project for a more granular view. Learn more in the full [Projects documentation](/product/projects/).
 
-- **Explore** - Sentry offers multiple ways to search and investigate your application's data — including your app's [traces](/product/trace-explorer/), [metrics](/product/metrics/), [profiles](/product/profiling/), [replays](/product/session-replay/), and [logs](/product/logs/) — to get the information you need to debug issues more quickly and easily. Use the [Discover](/product/discover-queries/) page to query events across environments, visualize the results, and unlock insights into the health of your entire system.
+- **Explore** - Sentry offers multiple ways to search and investigate your application's data — including your app's [errors](/product/errors/), [traces](/product/trace-explorer/), [metrics](/product/metrics/), [profiles](/product/profiling/), [replays](/product/session-replay/), and [logs](/product/logs/) — to get the information you need to debug issues more quickly and easily.
 
 - **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/).
 

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

@@ -243,4 +243,4 @@ Dynamic sampling ensures complete traces by retaining all transactions associate
 
 Use the [Trace Explorer](/product/trace-explorer/) 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/dashboards/sentry-dashboards/) and [Discover](/product/discover-queries/), you can also view trace data in the [Trace View](/concepts/key-terms/tracing/trace-view/) page.
+Through [Dashboards](/product/dashboards/sentry-dashboards/) and [Traces](/product/trace-explorer/), you can also view trace data in the [Trace View](/concepts/key-terms/tracing/trace-view/) page.

docs/concepts/key-terms/tracing/trace-view.mdx

@@ -10,81 +10,34 @@ description: >-
 og_image: /og-images/concepts-key-terms-tracing-trace-view.png
 ---
 
-The Trace View page is designed to be your one-stop-shop when debugging performance or errors. It gives you full context on what was happening when an error or performance issue occurred, all in one place. The waterfall Trace View allows you to see everything that may have occurred during a trace, including errors, performance issues, and any profiles that may have been collected.
+The Trace View page is designed to be your one-stop-shop when debugging performance or errors. It gives you full context on what was happening when an error or performance issue occurred, all in one place. The waterfall Trace View allows you to see everything that may have occurred during a trace, including errors, performance issues, logs, and any profiles that may have been collected.
 
-In addition, looking at the Trace View allows you to drill down into a single trace so you can visualize the high-level transactions and spans that took place within that trace. This makes debugging slow services, identifying related errors, and rooting out bottlenecks easier and faster, since you no longer have to navigate around multiple pages of the Sentry product.
+In addition, looking at the Trace View allows you to drill down into a single trace so you can visualize the high-level spans that took place within that trace. This makes debugging slow services, identifying related errors, and rooting out bottlenecks easier and faster, since you no longer have to navigate around multiple pages of the Sentry product.
+
+![Trace View](./img/trace-view.png)
 
 ## Product Walkthrough: Trace View Page
 
-Sentry's default visualization of a trace is a waterfall-like structure, where the entries (transactions and spans) in the list are organized chronologically and through ancestry (child spans will fall under their parents). This allows you to follow the order of operations and drill into sub-operations.
+Sentry's default visualization of a [trace](/concepts/key-terms/tracing/) is a waterfall-like structure, where the entries in the list are organized chronologically and through ancestry (child spans will fall under their parents). This allows you to follow the order of operations and drill into sub-operations.
 
 On the left side is a list of operations, and on the right is their duration and any events, such as errors, which may have occurred in that timeframe.
 
-By default, the waterfall view shows a list of transactions. If you need more granular data and want to see spans as well, click "+" to the left of a transaction to expand the waterfall. The waterfall view helps surface any performance issues or profiles collected during a given timeframe.
-
-<br />
-
-<div
-  style={{
-    height: "0px",
-    paddingBottom: "calc(66.66% + 41px)",
-    position: "relative",
-    width: "100%",
-  }}
->
-  <iframe
-    src="https://demo.arcade.software/25H9paIDvBOQp5T3pFeW?embed&show_copy_link=true"
-    frameborder="0"
-    loading="lazy"
-    webkitallowfullscreen
-    mozallowfullscreen
-    allowfullscreen
-    allow="clipboard-write; fullscreen;"
-    style={{
-      colorScheme: "light",
-      height: "100%",
-      left: "0px",
-      position: "absolute",
-      top: "0px",
-      width: "100%",
-    }}
-  ></iframe>
-</div>
-
-<br />
+<Arcade src="https://demo.arcade.software/u9sthw4r7MH1jehzjLuP?embed" />
 
 ### Previous and Next Traces
 
 As users interact with an application, they generate multiple traces. For example, when a user loads a page in their browser and then navigates to another page, this creates two separate traces: one for the initial pageload and another for the subsequent navigation. By default, Sentry will link the traces together.
 
 If linked traces are available, you will see "Previous" or "Next" buttons next to the search bar and "Open in Explore" button, near the top of the trace view. These buttons allow you to navigate between traces that occurred before or after the current one.
 
-![Previous and next trace links](./img/trace-view-links.png)
-
 ### Helpful Tips
 
-Because debugging often involves multiple people or teams, we've made it easy to draw attention to specific areas of the trace and share a link that shows what you've highlighted with your colleagues. To do this, click on the row you'd like to draw attention to and share the resulting URL. Your colleague will see exactly what you want them to.
+Because debugging often involves multiple people or teams, Sentry makes it easy to draw attention to specific areas of the trace and share a link that shows what you've highlighted with your colleagues. To do this, click on the row you'd like to draw attention to and share the resulting URL. Your colleague will see exactly what you want them to.
 
 Whatever you highlight will also be saved if you navigate away from the page and will still be there when you use your browser's back and forward buttons.
 
 If you're doing a comparison and want an easy way to go back and forth between highlighted areas of interest in your trace, you can pin the tabs. When a tab is pinned, the view will be persistent throughout your session.
 
-<br />
-<Arcade src="https://demo.arcade.software/yP3PFytK0ckfetjJTe52?embed&show_copy_link=true" />
-<br />
-Sometimes, duration gaps between entries can be small, but critical to your debugging
-effort. That's why the Trace View enables you to zoom into certain areas of the trace,
-either by double clicking on row elements (which zooms into the row) or by using
-your scroll wheel.
-<br />
-<Arcade src="https://demo.arcade.software/U8JbMjFJR1KRiP4G4j4E?embed&show_copy_link=true" />
-<br />
-The Trace View has other features like search, which makes it easy to visualize matching
-spans that you can then iterate over using the up or down arrows. You can also tailor
-the layout to your preference.
-
-We're going to continue adding features that enable you to perform efficient investigation into whatever issues you might be facing. If you have feedback or requests, please share it with us. We'd love to hear how we can make your life easier and your users happier.
-
 ## Troubleshooting
 
 ### Orphan Traces and Broken Subtraces

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/discover-queries/), [Sentry Dashboards](/product/dashboards/sentry-dashboards/), and [Monitors](/product/monitors-and-alerts/monitors/).
+`OR` and `AND` search conditions are only available for [Explore](/concepts/key-terms/enrich-data/#explore), [Sentry Dashboards](/product/dashboards/sentry-dashboards/), and [Monitors](/product/monitors-and-alerts/monitors/).
 
 </Alert>
 

docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx

@@ -223,7 +223,7 @@ With this feature, the SDK differentiates between four different app start types
 - **Prewarmed cold start**
 - **Prewarmed warm start**
 
-You can filter for different app start types in [Discover](/product/discover-queries/) with `app_start_type:cold.prewarmed`, `app_start_type:warm.prewarmed`, `app_start_type:cold`, and `app_start_type:warm`.
+You can filter for different app start types in [Trace Explorer](/product/trace-explorer/) with `app_start_type:cold.prewarmed`, `app_start_type:warm.prewarmed`, `app_start_type:cold`, and `app_start_type:warm`.
 
 To disable prewarmed app start tracing:
 

docs/product/dashboards/index.mdx

@@ -37,9 +37,9 @@ You can also use these dashboards as templates by duplicating them to create you
 
 You can make [custom dashboards](/product/dashboards/custom-dashboards/) by duplicating an existing dashboard, using [AI to generate a dashboard](/product/dashboards/custom-dashboards/#ai-generated-dashboards) with natural language, or starting from scratch by pressing the **Create Dashboard** button. Custom dashboards enable you to create views tailored to your organization's needs. For example, you may want to track performance of a specific feature, or track errors by a specific team's ownership. Once in edit mode, use the same filters you use to drill into a dashboard to customize your dashboard.
 
-## Open Dashboard Widgets in Discover and Issues
+## Open Dashboard Widgets in Explore and Issues
 
-Each dashboard [widget](/product/dashboards/widget-builder/) has an ellipsis that opens a context menu. From here, depending on the type of data the widget shows, you can open the widget in [Discover](/product/discover-queries/) or [Issues](/product/issues/) to get more information.
+Each dashboard [widget](/product/dashboards/widget-builder/) has an ellipsis that opens a context menu. From here, depending on the type of data the widget shows, you can open the widget in different explorers: [Errors](/product/errors/), [Traces](/product/trace-explorer/), [Logs](/product/logs/), [Session Replays](/product/session-replay/web/), and [Metrics](/product/metrics/) to get more information.
 
 ## Widget Viewer
 

docs/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts.mdx

@@ -62,7 +62,7 @@ First Paint (FP) measures the amount of time the first pixel takes to appear in
 ### First Input Delay (FID)
 
 <Alert>
-As of March 12, 2024, First Input Delay (FID) was replaced as a Core Web Vital by INP. While Sentry no longer includes FID in our performance score calculations nor on the **Web Vitals** performance page, we continue to collect FID metrics. You can query FID measurements in [Discover](/product/discover-queries/).
+As of March 12, 2024, First Input Delay (FID) was replaced as a Core Web Vital by INP. While Sentry no longer includes FID in our performance score calculations nor on the **Web Vitals** performance page, we continue to collect FID metrics. You can query FID measurements in [Traces](/concepts/key-terms/tracing/).
 </Alert>
 
 [First Input Delay (FID)](https://web.dev/fid/) measures response time when a user tries to interact with the viewport by clicking a button, link, or any other custom JavaScript controller. FID data is critical for understanding whether interactions on an application page are successful or not.

docs/product/dashboards/sentry-dashboards/transaction-summary.mdx

@@ -57,7 +57,7 @@ On initial load, the table displays slow occurrences of the transaction along wi
 
 The table also updates dynamically if you change any of the project, environment, or date range filters or when you drill in on a latency segment (applicable when viewing the Latency Histogram).
 
-When viewing transactions, you may want to create more curated views. Click "Open in Discover" above the table to create a custom query to investigate further. For more details, see the full documentation for the Discover [Query Builder](/product/discover-queries/query-builder/).
+When viewing transactions, you may want to create more curated views. Click "Open in Trace Explorer" above the table to create a custom query to investigate further. For more details, see the full documentation on [Traces and Spans](/product/trace-explorer/).
 
 <Alert>
 

docs/product/dashboards/widget-builder/index.mdx

@@ -18,7 +18,7 @@ Some of these options are standard and displayed for all widgets, but others are
 In the dataset selection step, choose which type of data you would like to use in your widget. Available datasets include: [errors](#errors), [spans](#spans), [logs](#logs), [issues](#issues), [releases](#releases), and [application metrics](#application-metrics).
 
 ### Errors
-Choosing "Errors" allows you to query and aggregate error events in the same way you would for a [Discover Query](/product/discover-queries/). This data is comprised of errors that occur in your application, which Sentry will use to group into issues, for example:
+Choosing "Errors" allows you to query and aggregate error events in the same way you would on the [Errors](/product/errors/) page. This data is comprised of errors that occur in your application, which Sentry will use to group into issues, for example:
 
 - Users most affected by errors
 
@@ -74,7 +74,7 @@ Choosing "Releases (sessions, crash rates)" allows you to query properties speci
 Transactions are deprecated in favor of spans. Use the [Spans](#spans) dataset for new widgets, or explore performance data in [Trace Explorer](/product/trace-explorer/).
 </Alert>
 
-Choosing "Transactions" allows you to query and aggregate transaction events in the same way you would for a [Discover Query](/product/discover-queries/). This data is comprised of events that track the performance of operations in your application.
+Choosing "Transactions" allows you to query and aggregate transaction events. This data is comprised of events that track the performance of operations in your application.
 
 ## Visualization Type
 
@@ -108,11 +108,11 @@ This visualization is useful when you want to compare values across different ca
 
 ### Table
 
-Table charts display the results of a [Discover Query](/product/discover-queries/). This visualization is well suited to showing key fields and related aggregates. For example “duration percentiles for the most frequently visited transaction names”. You can also choose to display [issues](/product/issues/) data in a table visualization using the [dataset selector](/product/dashboards/widget-builder/#choose-your-dataset).
+Table charts display the results of a query. This visualization is well suited to showing key fields and related aggregates. For example “duration percentiles for the most frequently visited transaction names”. You can also choose to display [issues](/product/issues/) data in a table visualization using the [dataset selector](/product/dashboards/widget-builder/#choose-your-dataset).
 
 ### Big Number
 
-A big number visualization displays the current value of a single function or [equation](/product/discover-queries/query-builder/query-equations/). This visualization is well suited for high-level aggregates. An example scenario would be “p95 of all transactions”.
+A big number visualization displays the current value of a single function. This visualization is well suited for high-level aggregates. An example scenario would be “p95 of all transactions”.
 
 ### Markdown
 
@@ -142,9 +142,7 @@ Heatmaps are a great way to visualize value density over time. This is ideal for
 
 The option to set columns is only available for [table visualizations](/product/dashboards/widget-builder/#table).
 
-By default, the first column is already configured for you, but you can update it. To add more columns, which stacks events, add [functions](/product/discover-queries/query-builder/#stacking-functions) (`f(x)`) that can take in parameters. [Field and tag columns](/concepts/search/searchable-properties/#event-properties) will help you view more details about the events (for example, `title` to see the description of an issue or `users` to see how many users it's affecting).
-
-You can also add equations to your query using the table columns as equation variables, and the results will be displayed in the query results table. Learn more in [Adding Query Equations](/product/discover-queries/query-builder/query-equations/).
+By default, the first column is already configured for you, but you can update it. To add more columns, which stacks events, add [functions](/product/errors/#stacking-functions) (`f(x)`) that can take in parameters. [Field and tag columns](/concepts/search/searchable-properties/#event-properties) will help you view more details about the events (for example, `title` to see the description of an issue or `users` to see how many users it's affecting).
 
 Next to each column and equation, you have the option to set an alias that will replace the column name in the table header.