feat: Flatten Explore section into Product sidebar with section headers

docs/ai/index.mdx

@@ -87,14 +87,14 @@ Looking for Sentry's AI-powered debugging features? Sentry uses AI to help you d
     className="w-full md:w-[calc(50%-12px)]"
   />
   <LinkCard
-    href="/product/explore/session-replay/replay-details/#ai-powered-replay-summary-web-only"
+    href="/product/session-replay/replay-details/#ai-powered-replay-summary-web-only"
     iconSrc="/ai/img/IconTable.svg"
     title="AI Replay Summaries"
     description="Get AI-generated summaries of session replays to debug issues faster."
     className="w-full md:w-[calc(50%-12px)]"
   />
   <LinkCard
-    href="/product/explore/trace-explorer/"
+    href="/product/trace-explorer/"
     iconSrc="/ai/img/IconCompass.svg"
     title="AI-Powered Query Builder"
     description="Use natural language queries to search your traces and spans data in Trace Explorer."

docs/ai/monitoring/agents/sampling.mdx

@@ -125,7 +125,7 @@ If 100% trace sampling isn't feasible at your scale, you can supplement lower tr
 
 ### Metrics
 
-Emit [custom Application Metrics](/product/explore/metrics/) on every LLM call to track token usage, latency, and error rates independently of traces:
+Emit [custom Application Metrics](/product/metrics/) on every LLM call to track token usage, latency, and error rates independently of traces:
 
 ```javascript
 import * as Sentry from "@sentry/node";
@@ -166,7 +166,7 @@ sentry_sdk.metrics.distribution(
 
 ### Structured Logs
 
-Use [Sentry structured logging](/product/explore/logs/) to capture per-call details:
+Use [Sentry structured logging](/product/logs/) to capture per-call details:
 
 ```javascript
 Sentry.logger.info("LLM call completed", {

docs/concepts/data-management/filtering/index.mdx

@@ -87,7 +87,7 @@ We consider a transaction to be a health check if its name matches one of the fo
 
 ## Session Replay Filtering
 
-Inbound data filters have partial support for [Session Replay](/product/explore/session-replay/). Only a subset of the available inbound filters apply to Session Replays.
+Inbound data filters have partial support for [Session Replay](/product/session-replay/). Only a subset of the available inbound filters apply to Session Replays.
 
 The following inbound filters **do** apply to Session Replays:
 
@@ -122,7 +122,7 @@ Once applied, you can track the filtered events (numbers and cause) using the gr
 
 ## Logs Filtering
 
-Inbound data filters have partial support for [Logs](/product/explore/logs/). Only a subset of the available inbound filters apply to Logs.
+Inbound data filters have partial support for [Logs](/product/logs/). Only a subset of the available inbound filters apply to Logs.
 
 The following inbound filters **do** apply to Logs:
 
@@ -144,7 +144,7 @@ The following inbound filters **do not** apply to Logs:
 
 ## Application Metrics Filtering
 
-Inbound data filters have partial support for [Application Metrics](/product/explore/metrics/). The following inbound filters **do** apply to Application Metrics:
+Inbound data filters have partial support for [Application Metrics](/product/metrics/). The following inbound filters **do** apply to Application Metrics:
 
 - **Application Metrics** - Filters Application Metrics by metric name (supports glob pattern matching, for example `my_metric.*`)
 - **Releases** - Filters Application Metrics from specific release versions

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

@@ -67,7 +67,7 @@ For instance, the Discover query below displays all the errors (total of 143 eve
 
 ![Discover Query](./img/004.png)
 
-Learn more in [Discover](/product/explore/discover-queries/).
+Learn more in [Discover](/product/discover-queries/).
 
 ### 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, 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/).
+- **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.
 
 - **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/sample-rates.mdx

@@ -44,4 +44,4 @@ Learn more about [tracing](/product/tracing/) in Sentry.
 
 - **replaysOnErrorSampleRate** - The sample rate for replays that are recorded when an error happens. This type of replay will record up to a minute of events prior to the error and continue recording until the session ends. 1.0 captures all sessions with an error, and 0 captures none.
 
-Learn more about [session replay](/product/explore/session-replay/) in Sentry.
+Learn more about [session replay](/product/session-replay/) in Sentry.

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

@@ -20,7 +20,7 @@ Distributed tracing provides a connected view of your application from frontend
 
 A tracing tool focuses on what happened (and when), logging events during a program's execution across multiple systems. Traces often include timestamps, allowing durations to be calculated, but their purpose is broader, showing how interconnected systems interact and how problems in one can affect another. While tracing can be useful if instrumented in just the frontend or backend, it's most powerful when set up for your full stack (distributed tracing).
 
-It's important to note that tracing is not [profiling](/product/explore/profiling/). A profiler measures various aspects of an application's operation, resulting in a statistical summary. While both diagnose application problems, they differ in what they measure and how data is recorded.
+It's important to note that tracing is not [profiling](/product/profiling/). A profiler measures various aspects of an application's operation, resulting in a statistical summary. While both diagnose application problems, they differ in what they measure and how data is recorded.
 
 
 Learn more in our [tracing documentation](/product/sentry-basics/tracing/).
@@ -229,6 +229,6 @@ Dynamic sampling ensures complete traces by retaining all transactions associate
 
 ## Viewing Trace Data
 
-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.
+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/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/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/dashboards/sentry-dashboards/backend/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/trace-explorer/) 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?
 
@@ -49,7 +49,7 @@ If you want more information, click on any trace ID. This will take you to the [
 
 ![A detailed view of the Sentry Traces page showing an expanded trace and spans](./img/Trace-view-page.png)
 
-Alternatively, you can use the search bar to look for spans by name, project, or other criteria. You can also use the tags section to filter spans by specific tags. Learn more about the Sentry [Trace Explorer](/product/explore/traces/).
+Alternatively, you can use the search bar to look for spans by name, project, or other criteria. You can also use the tags section to filter spans by specific tags. Learn more about the Sentry [Trace Explorer](/product/trace-explorer/).
 
 ![An illustrated image of the anatomy of a trace, showing 8 span blocks cascading in a waterfall pattern.](./img/Traces-details-page.png)
 

docs/concepts/key-terms/tracing/span-metrics.mdx

@@ -6,7 +6,7 @@ sidebar_order: 10
 
 <Alert title="Looking for standalone counters, gauges, or distributions?">
 
-Span metrics are great for enriching your existing traces with custom data. If you need metrics that are independent of tracing — such as business event counters, success/failure rates, or aggregates that aren't affected by trace sampling — use [Application Metrics](/product/explore/metrics/) instead.
+Span metrics are great for enriching your existing traces with custom data. If you need metrics that are independent of tracing — such as business event counters, success/failure rates, or aggregates that aren't affected by trace sampling — use [Application Metrics](/product/metrics/) instead.
 
 </Alert>
 

docs/concepts/otlp/forwarding/sources/aws-cloudwatch.mdx

@@ -197,4 +197,4 @@ service:
 - [AWS CloudWatch Receiver Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/awscloudwatchreceiver)
 - [AWS SDK Authentication](https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html)
 - [Sentry OpenTelemetry Collector Configuration](/concepts/otlp/forwarding/pipelines/collector/)
-- [Sentry Logs](/product/explore/logs/)
+- [Sentry Logs](/product/logs/)

docs/concepts/otlp/forwarding/sources/kafka.mdx

@@ -193,4 +193,4 @@ The Kafka Receiver supports various encodings for different signal types:
 
 - [Kafka Receiver Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/kafkareceiver)
 - [Sentry OpenTelemetry Collector Configuration](/concepts/otlp/forwarding/pipelines/collector/)
-- [Sentry Logs](/product/explore/logs/)
+- [Sentry Logs](/product/logs/)

docs/concepts/otlp/forwarding/sources/nginx.mdx

@@ -288,4 +288,4 @@ To run in the background:
 
 - [File Log Receiver Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver)
 - [Sentry OpenTelemetry Collector Configuration](/concepts/otlp/forwarding/pipelines/collector/)
-- [Sentry Logs](/product/explore/logs/)
+- [Sentry Logs](/product/logs/)

docs/concepts/otlp/forwarding/sources/syslog.mdx

@@ -163,4 +163,4 @@ log {
 
 - [Syslog Receiver Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/syslogreceiver)
 - [Sentry OpenTelemetry Collector Configuration](/concepts/otlp/forwarding/pipelines/collector/)
-- [Sentry Logs](/product/explore/logs/)
+- [Sentry Logs](/product/logs/)

docs/concepts/otlp/forwarding/sources/windows-events.mdx

@@ -237,4 +237,4 @@ C:\otel-collector\otelcol-contrib.exe --config C:\otel-collector\config_debug.ya
 
 - [Windows Event Log Receiver Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/windowseventlogreceiver)
 - [Sentry OpenTelemetry Collector Configuration](/concepts/otlp/forwarding/pipelines/collector/)
-- [Sentry Logs](/product/explore/logs/)
+- [Sentry Logs](/product/logs/)

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/), [Sentry Dashboards](/product/dashboards/sentry-dashboards/), and [Monitors](/product/monitors-and-alerts/monitors/).
+`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/).
 
 </Alert>
 

docs/concepts/search/searchable-properties/session-replay.mdx

@@ -4,7 +4,7 @@ description: "Learn more about searchable session replay properties."
 sidebar_order: 30
 ---
 
-[Session Replay](/product/explore/session-replay/) provides a video-like reproduction of user interactions on a site or web app. All user interactions, including page visits, mouse movements, clicks, and scrolls, are captured, helping developers connect the dots between a known issue and how a user experienced it in the UI.
+[Session Replay](/product/session-replay/) provides a video-like reproduction of user interactions on a site or web app. All user interactions, including page visits, mouse movements, clicks, and scrolls, are captured, helping developers connect the dots between a known issue and how a user experienced it in the UI.
 
 You can search by session replay properties on the **Replay** page.
 
@@ -102,7 +102,7 @@ The `title` of an element that was clicked. For example, `Save this comment` wou
 
 ### `count_dead_clicks`
 
-The number of [dead clicks](/product/explore/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds%20(i.e.%20no%20HTML%20was%20added%2C%20removed%2C%20or%20updated%3B%20no%20visual%20changes%20were%20observed%20in%20the%20page).) within a replay.
+The number of [dead clicks](/product/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds%20(i.e.%20no%20HTML%20was%20added%2C%20removed%2C%20or%20updated%3B%20no%20visual%20changes%20were%20observed%20in%20the%20page).) within a replay.
 
 - **Type:** number
 
@@ -114,7 +114,7 @@ The number of errors within a replay.
 
 ### `count_rage_clicks`
 
-The number of [rage clicks](/product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks) within a replay.
+The number of [rage clicks](/product/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks) within a replay.
 
 - **Type:** number
 
@@ -138,7 +138,7 @@ The number of URLs that the user visited during a replay recording.
 
 ### `dead.selector`
 
-Similar to the `click.selector` search property, but only queries on [dead clicks](/product/explore/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds%20(i.e.%20no%20HTML%20was%20added%2C%20removed%2C%20or%20updated%3B%20no%20visual%20changes%20were%20observed%20in%20the%20page).). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
+Similar to the `click.selector` search property, but only queries on [dead clicks](/product/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds%20(i.e.%20no%20HTML%20was%20added%2C%20removed%2C%20or%20updated%3B%20no%20visual%20changes%20were%20observed%20in%20the%20page).). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
 
 - **Type:** string
 
@@ -228,7 +228,7 @@ The id of the project.
 
 ### `rage.selector`
 
-Similar to the `click.selector` search property, but only queries on [rage clicks](/product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
+Similar to the `click.selector` search property, but only queries on [rage clicks](/product/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
 
 - **Type:** string
 

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

@@ -8,7 +8,7 @@ Spans are the underlying data element captured in Sentry SDKs that together make
 
 You can search by span properties in the following [Sentry](https://sentry.io) pages:
 
-- [Traces](/product/explore/traces/) - when searching for a trace containing spans with matching properties
+- [Traces](/product/trace-explorer/) - when searching for a trace containing spans with matching properties
 
 When you search for span properties within the **Traces** page, the search will return any trace that contains _one or more spans_ that match your span properties filter.