diff --git a/docs/cli/metrics.mdx b/docs/cli/metrics.mdx index d4beee44dbe58..8da8324801634 100644 --- a/docs/cli/metrics.mdx +++ b/docs/cli/metrics.mdx @@ -4,7 +4,7 @@ sidebar_order: 5 description: "Learn how Sentry's command line interface can be used for sending metrics." --- Metrics help you track and visualize the data points you care about, making it easier to monitor your application's health and identify issues. -Learn more about [Metrics](/product/metrics). +Learn more about [Metrics](/product/explore/metrics). ## Requirements - [Install](/product/cli/installation) the Sentry CLI (min v2.32.0). @@ -35,7 +35,7 @@ sentry-cli send-metric increment -n "MyMetric" -u "MyUnit" -t "tag1:val1","tag2: ``` The metric's name, unit, and tags will undergo normalization to only include supported characters. -Learn more about [Limits and Restrictions](/product/metrics/#limits-and-restrictions). +Learn more about [Limits and Restrictions](/product/explore/metrics/#limits-and-restrictions). ### Counters To increment a counter metric by one, you only need to provide the `--name` or `-n` parameter. diff --git a/docs/concepts/key-terms/enrich-data/index.mdx b/docs/concepts/key-terms/enrich-data/index.mdx index 020e0ee219718..533a9bfcef8b1 100644 --- a/docs/concepts/key-terms/enrich-data/index.mdx +++ b/docs/concepts/key-terms/enrich-data/index.mdx @@ -64,7 +64,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/discover-queries/). +Learn more in [Discover](/product/explore/discover-queries/). ### Ownership Rules diff --git a/docs/concepts/key-terms/key-terms.mdx b/docs/concepts/key-terms/key-terms.mdx index dd2920e4571c0..831e98c5e2b13 100644 --- a/docs/concepts/key-terms/key-terms.mdx +++ b/docs/concepts/key-terms/key-terms.mdx @@ -50,7 +50,7 @@ Each of these key features in [sentry.io](https://sentry.io) is represented by a - **Dashboards** - Provide you with a broad overview of your application’s health by allowing you to navigate through error and performance data across multiple projects. Dashboards are made up of one or more widgets, and each widget visualizes one or more **Discover** or **Issues** queries. Learn more in the full [Dashboards documentation](/product/dashboards/). -- **Discover** - Allows you to query events across environments, providing you with visibility into your errors and transactions and unlocking insights into the health of your entire system. The **Discover** page visualizes the results of queries. Learn more in the full [Discover documentation](/product/discover-queries/). +- **Discover** - Allows you to query events across environments, providing you with visibility into your errors and transactions and unlocking insights into the health of your entire system. The **Discover** page visualizes the results of queries. Learn more in the full [Discover documentation](/product/explore/discover-queries/). - **Issues** - Displays information about grouped problems in your application. From here, you can go to the **Issue Details** page for a more granular view of any issue. Learn more in the full [Issues documentation](/product/issues/). diff --git a/docs/concepts/key-terms/tracing/distributed-tracing.mdx b/docs/concepts/key-terms/tracing/distributed-tracing.mdx index c3a9bd77a8ab2..d868f32a2753b 100644 --- a/docs/concepts/key-terms/tracing/distributed-tracing.mdx +++ b/docs/concepts/key-terms/tracing/distributed-tracing.mdx @@ -243,4 +243,4 @@ Put simply: as a result of this head-based approach, where the decision is made ## Viewing Trace Data -Through [Performance](/product/performance/) and [Discover](/product/discover-queries/), you can view trace data in the [Trace Details](/concepts/key-terms/tracing/trace-view/) page. +Through [Performance](/product/performance/) and [Discover](/product/explore/discover-queries/), you can view trace data in the [Trace Details](/concepts/key-terms/tracing/trace-view/) page. diff --git a/docs/concepts/key-terms/tracing/event-detail.mdx b/docs/concepts/key-terms/tracing/event-detail.mdx new file mode 100644 index 0000000000000..e69de29bb2d1d diff --git a/docs/concepts/search/index.mdx b/docs/concepts/search/index.mdx index 4dc1903889d7b..5147af698b153 100644 --- a/docs/concepts/search/index.mdx +++ b/docs/concepts/search/index.mdx @@ -50,7 +50,7 @@ Here are some examples of valid comparison operator searches: -`OR` and `AND` search conditions are only available for [Discover](/product/discover-queries/), [Performance](/product/performance/), and [Metric Alerts](/product/alerts-notifications/metric-alerts/). +`OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Performance](/product/performance/), and [Metric Alerts](/product/alerts-notifications/metric-alerts/). diff --git a/docs/concepts/search/searchable-properties/session-replay.mdx b/docs/concepts/search/searchable-properties/session-replay.mdx index 10d8e408c272c..4a7da864b65d4 100644 --- a/docs/concepts/search/searchable-properties/session-replay.mdx +++ b/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/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/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. 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](https://docs.sentry.io/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) within a replay. +The number of [dead clicks](https://docs.sentry.io/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) within a replay. - **Type:** number @@ -114,7 +114,7 @@ The number of errors within a replay. ### `count_rage_clicks` -The number of [rage clicks]() within a replay. +The number of [rage clicks]() within a replay. - **Type:** number @@ -132,7 +132,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](https://docs.sentry.io/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). 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 ``. 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](https://docs.sentry.io/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). 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 ``. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported. - **Type:** string @@ -216,7 +216,7 @@ The id of the project. ### `rage.selector` -Similar to the `click.selector` search property, but only queries on [rage clicks](). 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 ``. 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](). 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 ``. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported. - **Type:** string diff --git a/docs/organization/integrations/session-replay/index.mdx b/docs/organization/integrations/session-replay/index.mdx index 9a52924cf566a..93789d3e48647 100644 --- a/docs/organization/integrations/session-replay/index.mdx +++ b/docs/organization/integrations/session-replay/index.mdx @@ -6,7 +6,7 @@ description: "Learn more about third-party session replay integrations." -Looking for Sentry's built-in Session Replay product? Click here to learn more. +Looking for Sentry's built-in Session Replay product? Click here to learn more. diff --git a/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx index b425738d0615d..806c90892c497 100644 --- a/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx @@ -105,7 +105,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 [Discover](/product/explore/discover-queries/) with `app_start_type:cold.prewarmed`, `app_start_type:warm.prewarmed`, `app_start_type:cold`, and `app_start_type:warm`. To enable prewarmed app start tracing: diff --git a/docs/platforms/dotnet/common/profiling/index.mdx b/docs/platforms/dotnet/common/profiling/index.mdx index 8b3f31ccbfdc0..c77888bc35fe8 100644 --- a/docs/platforms/dotnet/common/profiling/index.mdx +++ b/docs/platforms/dotnet/common/profiling/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 5000 -With [profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real user devices in production to give you a complete picture of how your application performs in a variety of environments. +With [profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real user devices in production to give you a complete picture of how your application performs in a variety of environments. diff --git a/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx b/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx index 593632951437b..f6b739e95ad9a 100644 --- a/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx @@ -24,6 +24,6 @@ notSupported: _Import name: `Sentry.browserProfilingIntegration`_ -[Profiling](/product/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment. +[Profiling](/product/explore/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment. Read more about setting up Profiling. diff --git a/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx b/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx index 47dbd81a803f4..f6a425ccfae62 100644 --- a/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx @@ -24,6 +24,6 @@ supported: _Import name: `Sentry.nodeProfilingIntegration`_ -[Profiling](/product/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment. +[Profiling](/product/explore/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment. Read more about setting up Profiling. diff --git a/docs/platforms/javascript/common/configuration/integrations/replay.mdx b/docs/platforms/javascript/common/configuration/integrations/replay.mdx index ba2f0c895d396..279f45609416f 100644 --- a/docs/platforms/javascript/common/configuration/integrations/replay.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/replay.mdx @@ -24,6 +24,6 @@ notSupported: _Import name: `Sentry.replayIntegration`_ -[Session Replay](/product/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a video-like reproduction of what was happening in the user's browser before, during, and after the issue. You can rewind and replay your application's DOM state and see key user interactions, like mouse clicks, scrolls, network requests, and console entries, in a single combined UI inspired by your browser's DevTools. +[Session Replay](/product/explore/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a video-like reproduction of what was happening in the user's browser before, during, and after the issue. You can rewind and replay your application's DOM state and see key user interactions, like mouse clicks, scrolls, network requests, and console entries, in a single combined UI inspired by your browser's DevTools. Read more about [setting up Session Replay](./../../../session-replay/). diff --git a/docs/platforms/javascript/common/session-replay/index.mdx b/docs/platforms/javascript/common/session-replay/index.mdx index 3eb91dd19a1d8..998ff782ccdc2 100644 --- a/docs/platforms/javascript/common/session-replay/index.mdx +++ b/docs/platforms/javascript/common/session-replay/index.mdx @@ -21,7 +21,7 @@ description: "Learn how to enable Session Replay in your app if it is not alread -[Session Replay](/product/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a video-like reproduction of what was happening in the user's browser before, during, and after the issue. You can rewind and replay your application's DOM state and see key user interactions, like mouse clicks, scrolls, network requests, and console entries, in a single combined UI inspired by your browser's DevTools. +[Session Replay](/product/explore/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a video-like reproduction of what was happening in the user's browser before, during, and after the issue. You can rewind and replay your application's DOM state and see key user interactions, like mouse clicks, scrolls, network requests, and console entries, in a single combined UI inspired by your browser's DevTools. By default, our Session Replay SDK masks all DOM text content, images, and user input, giving you heightened confidence that no sensitive data will leave the browser. To learn more, see Session Replay Privacy. diff --git a/docs/platforms/javascript/common/session-replay/troubleshooting.mdx b/docs/platforms/javascript/common/session-replay/troubleshooting.mdx index 52d889c722bbf..0b9a153428edf 100644 --- a/docs/platforms/javascript/common/session-replay/troubleshooting.mdx +++ b/docs/platforms/javascript/common/session-replay/troubleshooting.mdx @@ -106,7 +106,7 @@ Sentry.replayIntegration({ -The Sentry SDK attempts to minimize potential [performance overhead](/product/session-replay/performance-overhead/#how-is-session-replay-optimized) in a few different ways. For example, by keeping track of the number of DOM mutations that are happening then disabling recording when a large number of changes are detected. Many simultaneous mutations can slow down a web page whether Session Replay is installed or not, but when a large number of mutations happen, the Replay client can incur an additional slowdown because it records each change. +The Sentry SDK attempts to minimize potential [performance overhead](/product/explore/session-replay/performance-overhead/#how-is-session-replay-optimized) in a few different ways. For example, by keeping track of the number of DOM mutations that are happening then disabling recording when a large number of changes are detected. Many simultaneous mutations can slow down a web page whether Session Replay is installed or not, but when a large number of mutations happen, the Replay client can incur an additional slowdown because it records each change. If you're seeing the "A large number of mutations was detected" message while watching a replay, it means that your page could be optimized. For example, a dropdown list with thousands of entries could be refactored so that rows are virtualized where only the visible rows are rendered in the DOM. Another potential solution is to paginate the results fetch more data as the user scrolls through it. The SDK has a configuration that allows you to configure the limits before recording stops. diff --git a/docs/platforms/php/common/profiling/index.mdx b/docs/platforms/php/common/profiling/index.mdx index e173cbbaa5b78..d306e122faa5f 100644 --- a/docs/platforms/php/common/profiling/index.mdx +++ b/docs/platforms/php/common/profiling/index.mdx @@ -10,7 +10,7 @@ Profiling for PHP is supported with Sentry PHP SDK version `3.15.0` and above. -With [profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. +With [profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer). The Excimer PHP extension supports PHP 7.2 and up. diff --git a/docs/platforms/php/guides/laravel/profiling/index.mdx b/docs/platforms/php/guides/laravel/profiling/index.mdx index 2336778bd2b1c..4afad9164a6f0 100644 --- a/docs/platforms/php/guides/laravel/profiling/index.mdx +++ b/docs/platforms/php/guides/laravel/profiling/index.mdx @@ -10,7 +10,7 @@ Profiling for PHP is supported with Sentry Laravel SDK version `3.3.0` and above -With [Profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. +With [Profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer). The Excimer PHP extension supports PHP 7.2 and up. diff --git a/docs/platforms/php/guides/symfony/profiling/index.mdx b/docs/platforms/php/guides/symfony/profiling/index.mdx index 9d7259120ed42..0f9cb22a6f63c 100644 --- a/docs/platforms/php/guides/symfony/profiling/index.mdx +++ b/docs/platforms/php/guides/symfony/profiling/index.mdx @@ -10,7 +10,7 @@ Profiling for PHP is supported with Sentry Symfony SDK version `4.7.0` and above -With [Profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. +With [Profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer). The Excimer PHP extension supports PHP 7.2 and up. diff --git a/docs/platforms/react-native/profiling/troubleshooting/index.mdx b/docs/platforms/react-native/profiling/troubleshooting/index.mdx index 7359faebf0698..3a5fc1e1cc184 100644 --- a/docs/platforms/react-native/profiling/troubleshooting/index.mdx +++ b/docs/platforms/react-native/profiling/troubleshooting/index.mdx @@ -13,7 +13,7 @@ If you don't see any profiling data in [sentry.io](https://sentry.io), you can t ### Limitations -Because profile samples are collected at a fixed sampling frequency, we recommend checking if profiling's [Performance Overhead](/product/profiling/performance-overhead) is acceptable for your use case. Note that +Because profile samples are collected at a fixed sampling frequency, we recommend checking if profiling's [Performance Overhead](/product/explore/profiling/performance-overhead) is acceptable for your use case. Note that we're working on symbolication of the collected profiles which means that at the moment you'll see only function names but not resolved source file paths. As always, and especially since Profiling in React Native is an alpha feature, feedback is welcome on [Discord](https://discord.com/channels/621778831602221064/750735628932612096) or [GitHub](https://github.com/getsentry/sentry-react-native/issues/2668). diff --git a/docs/pricing/index.mdx b/docs/pricing/index.mdx index 784b52e0fa047..e4578b1d746ea 100644 --- a/docs/pricing/index.mdx +++ b/docs/pricing/index.mdx @@ -54,7 +54,7 @@ Performance Units can be used towards multiple Performance event types, dependin | Event Type | Unit Value | | |---|---|---| | Transactions | 1 Unit | Sent by SDKs with only [Tracing](/product/sentry-basics/tracing/) enabled | -| Transactions with Profiling | 1.3 Units | Sent by SDKs with both [Tracing](/product/sentry-basics/tracing/) & [Profiling](/product/profiling/) enabled | +| Transactions with Profiling | 1.3 Units | Sent by SDKs with both [Tracing](/product/sentry-basics/tracing/) & [Profiling](/product/explore/profiling/) enabled | | Total Performance Unit Volume | Team Prepaid | Team On-Demand | Business Prepaid | Business On-Demand | |---|---|---|---|---| diff --git a/docs/product/alerts/alert-types.mdx b/docs/product/alerts/alert-types.mdx index 83d152bf2f4d7..3b38b12b2c80e 100644 --- a/docs/product/alerts/alert-types.mdx +++ b/docs/product/alerts/alert-types.mdx @@ -111,4 +111,4 @@ The **Alert Details** page shows you the history of a metric alert rule for the ![Alert details illustrates a graph showing the performance of a transaction over time.](./img/alert-details-example.png) -The **Alert Details** page also includes a list of suspect issues or transactions related to the metric, to help pinpoint the root problem more quickly. You can see what might have caused the alert to be triggered, and then open the metric in **[Discover](/product/discover-queries)** to find more information. +The **Alert Details** page also includes a list of suspect issues or transactions related to the metric, to help pinpoint the root problem more quickly. You can see what might have caused the alert to be triggered, and then open the metric in **[Discover](/product/explore/discover-queries)** to find more information. diff --git a/docs/product/alerts/create-alerts/metric-alert-config.mdx b/docs/product/alerts/create-alerts/metric-alert-config.mdx index 0f473affcd076..2e37a7bddbb3d 100644 --- a/docs/product/alerts/create-alerts/metric-alert-config.mdx +++ b/docs/product/alerts/create-alerts/metric-alert-config.mdx @@ -62,7 +62,7 @@ Choose the time period over which to evaluate your metric. Your choices range be ## Filters -The following set of filters translates into a [Discover query](/product/discover-queries/) that is displayed in the chart at the top of the alert configuration page. +The following set of filters translates into a [Discover query](/product/explore/discover-queries/) that is displayed in the chart at the top of the alert configuration page. ### Project diff --git a/docs/product/dashboards/index.mdx b/docs/product/dashboards/index.mdx index 9d6f9103dedd3..ee7b87efbea5f 100644 --- a/docs/product/dashboards/index.mdx +++ b/docs/product/dashboards/index.mdx @@ -6,7 +6,7 @@ description: "Sentry's Dashboards provide a single view of your application's he -Sentry's Dashboards provide you with a broad overview of your application’s health by allowing you to navigate through error and performance data across multiple projects. Dashboards are made up of one or more widgets, and each widget visualizes one or more [Discover queries](/product/discover-queries/). +Sentry's Dashboards provide you with a broad overview of your application’s health by allowing you to navigate through error and performance data across multiple projects. Dashboards are made up of one or more widgets, and each widget visualizes one or more [Discover queries](/product/explore/discover-queries/). ![Widgets visualizing events, errors by country, affected users, and handled vs unhandled issues.](./img/dashboard-default.png) @@ -20,7 +20,7 @@ If you’d like to edit the default dashboard or build out multiple ones, each w ## Open Dashboard Widgets in Discover -Each Dashboard widget has an ellipsis that opens a context menu. From here, you can open the widget in [Discover](/product/discover-queries/) for to get more information. If a widget contains more than one query, you'll be prompted to select which query to view in **Discover**. +Each Dashboard widget has an ellipsis that opens a context menu. From here, you can open the widget in [Discover](/product/explore/discover-queries/) for to get more information. If a widget contains more than one query, you'll be prompted to select which query to view in **Discover**. ## Widget Viewer diff --git a/docs/product/dashboards/widget-builder/index.mdx b/docs/product/dashboards/widget-builder/index.mdx index 6fce91aa8db98..51edf044255cb 100644 --- a/docs/product/dashboards/widget-builder/index.mdx +++ b/docs/product/dashboards/widget-builder/index.mdx @@ -40,7 +40,7 @@ Each chart type allows you to solve different problems: ### 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 [Discover Query](/product/explore/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). ### Big Number @@ -52,7 +52,7 @@ In the dataset selection step, choose which type of data you would like to use i ### Errors & Transactions -Choosing "Errors and Transactions" allows you to query and aggregate error and transaction events in the same way you would for a [Discover Query](/product/discover-queries/). Some widget examples include: +Choosing "Errors and Transactions" allows you to query and aggregate error and transaction events in the same way you would for a [Discover Query](/product/explore/discover-queries/). Some widget examples include: - Tracking performance of an endpoint - Throughput by country @@ -78,9 +78,9 @@ Choosing "Releases (sessions, crash rates)" allows you to query properties speci 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](/product/sentry-basics/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). +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/explore/discover-queries/query-builder/#stacking-functions) (`f(x)`) that can take in parameters. [Field and tag columns](/product/sentry-basics/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/). +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/explore/discover-queries/query-builder/query-equations/). Next to each column and equation, you have the option to set an alias that will replace the column name in the table header. diff --git a/docs/product/discover-queries/img/001.png b/docs/product/explore/discover-queries/img/001.png similarity index 100% rename from docs/product/discover-queries/img/001.png rename to docs/product/explore/discover-queries/img/001.png diff --git a/docs/product/discover-queries/img/002.png b/docs/product/explore/discover-queries/img/002.png similarity index 100% rename from docs/product/discover-queries/img/002.png rename to docs/product/explore/discover-queries/img/002.png diff --git a/docs/product/discover-queries/img/003.png b/docs/product/explore/discover-queries/img/003.png similarity index 100% rename from docs/product/discover-queries/img/003.png rename to docs/product/explore/discover-queries/img/003.png diff --git a/docs/product/discover-queries/img/004.png b/docs/product/explore/discover-queries/img/004.png similarity index 100% rename from docs/product/discover-queries/img/004.png rename to docs/product/explore/discover-queries/img/004.png diff --git a/docs/product/discover-queries/img/005.png b/docs/product/explore/discover-queries/img/005.png similarity index 100% rename from docs/product/discover-queries/img/005.png rename to docs/product/explore/discover-queries/img/005.png diff --git a/docs/product/discover-queries/img/006.png b/docs/product/explore/discover-queries/img/006.png similarity index 100% rename from docs/product/discover-queries/img/006.png rename to docs/product/explore/discover-queries/img/006.png diff --git a/docs/product/discover-queries/img/007.png b/docs/product/explore/discover-queries/img/007.png similarity index 100% rename from docs/product/discover-queries/img/007.png rename to docs/product/explore/discover-queries/img/007.png diff --git a/docs/product/discover-queries/img/008.png b/docs/product/explore/discover-queries/img/008.png similarity index 100% rename from docs/product/discover-queries/img/008.png rename to docs/product/explore/discover-queries/img/008.png diff --git a/docs/product/discover-queries/img/009.png b/docs/product/explore/discover-queries/img/009.png similarity index 100% rename from docs/product/discover-queries/img/009.png rename to docs/product/explore/discover-queries/img/009.png diff --git a/docs/product/discover-queries/img/010.png b/docs/product/explore/discover-queries/img/010.png similarity index 100% rename from docs/product/discover-queries/img/010.png rename to docs/product/explore/discover-queries/img/010.png diff --git a/docs/product/discover-queries/img/012.png b/docs/product/explore/discover-queries/img/012.png similarity index 100% rename from docs/product/discover-queries/img/012.png rename to docs/product/explore/discover-queries/img/012.png diff --git a/docs/product/discover-queries/img/013.png b/docs/product/explore/discover-queries/img/013.png similarity index 100% rename from docs/product/discover-queries/img/013.png rename to docs/product/explore/discover-queries/img/013.png diff --git a/docs/product/discover-queries/img/014.png b/docs/product/explore/discover-queries/img/014.png similarity index 100% rename from docs/product/discover-queries/img/014.png rename to docs/product/explore/discover-queries/img/014.png diff --git a/docs/product/discover-queries/img/discover-event-details.png b/docs/product/explore/discover-queries/img/discover-event-details.png similarity index 100% rename from docs/product/discover-queries/img/discover-event-details.png rename to docs/product/explore/discover-queries/img/discover-event-details.png diff --git a/docs/product/discover-queries/img/discover-facet-map.png b/docs/product/explore/discover-queries/img/discover-facet-map.png similarity index 100% rename from docs/product/discover-queries/img/discover-facet-map.png rename to docs/product/explore/discover-queries/img/discover-facet-map.png diff --git a/docs/product/discover-queries/img/discover-homepage.png b/docs/product/explore/discover-queries/img/discover-homepage.png similarity index 100% rename from docs/product/discover-queries/img/discover-homepage.png rename to docs/product/explore/discover-queries/img/discover-homepage.png diff --git a/docs/product/discover-queries/img/discover-results.png b/docs/product/explore/discover-queries/img/discover-results.png similarity index 100% rename from docs/product/discover-queries/img/discover-results.png rename to docs/product/explore/discover-queries/img/discover-results.png diff --git a/docs/product/discover-queries/img/discover-table-cell.png b/docs/product/explore/discover-queries/img/discover-table-cell.png similarity index 100% rename from docs/product/discover-queries/img/discover-table-cell.png rename to docs/product/explore/discover-queries/img/discover-table-cell.png diff --git a/docs/product/discover-queries/img/trace-details-view.png b/docs/product/explore/discover-queries/img/trace-details-view.png similarity index 100% rename from docs/product/discover-queries/img/trace-details-view.png rename to docs/product/explore/discover-queries/img/trace-details-view.png diff --git a/docs/product/discover-queries/index.mdx b/docs/product/explore/discover-queries/index.mdx similarity index 97% rename from docs/product/discover-queries/index.mdx rename to docs/product/explore/discover-queries/index.mdx index 5a8cf445fb3b3..ca413f1de1a2f 100644 --- a/docs/product/discover-queries/index.mdx +++ b/docs/product/explore/discover-queries/index.mdx @@ -6,7 +6,7 @@ description: "Discover is a powerful query engine that allows you to query all y -This feature is available only if your organization is on either a Business or Trial Plan, with the exception of the ["All Events" pre-built query](/product/discover-queries/#pre-built-queries), which is available on Team plans or higher. +This feature is available only if your organization is on either a Business or Trial Plan, with the exception of the ["All Events" pre-built query](/product/explore/discover-queries/#pre-built-queries), which is available on Team plans or higher. @@ -51,7 +51,7 @@ From the **Discover** page, you can build a " | sha1sum -c - On the **Discover** page, each saved query card has an ellipsis that will open a context menu. Delete the query from here. You can also delete the query within Query Results view by clicking the trash can in the upper right. -For more details on how to view saved queries, see the [full documentation on Discover](/product/discover-queries/) +For more details on how to view saved queries, see the [full documentation on Discover](/product/explore/discover-queries/) diff --git a/docs/product/discover-queries/query-builder/img/add_equation.gif b/docs/product/explore/discover-queries/query-builder/img/add_equation.gif similarity index 100% rename from docs/product/discover-queries/query-builder/img/add_equation.gif rename to docs/product/explore/discover-queries/query-builder/img/add_equation.gif diff --git a/docs/product/discover-queries/query-builder/query-equations.mdx b/docs/product/explore/discover-queries/query-builder/query-equations.mdx similarity index 100% rename from docs/product/discover-queries/query-builder/query-equations.mdx rename to docs/product/explore/discover-queries/query-builder/query-equations.mdx diff --git a/docs/product/discover-queries/standard-fields.json b/docs/product/explore/discover-queries/standard-fields.json similarity index 100% rename from docs/product/discover-queries/standard-fields.json rename to docs/product/explore/discover-queries/standard-fields.json diff --git a/docs/product/discover-queries/uncover-trends.mdx b/docs/product/explore/discover-queries/uncover-trends.mdx similarity index 100% rename from docs/product/discover-queries/uncover-trends.mdx rename to docs/product/explore/discover-queries/uncover-trends.mdx diff --git a/docs/product/explore/index.mdx b/docs/product/explore/index.mdx new file mode 100644 index 0000000000000..f8a4aa3ea16df --- /dev/null +++ b/docs/product/explore/index.mdx @@ -0,0 +1,11 @@ +--- +title: Explore +sidebar_order: 40 +description: Learn about the different ways you can explore your data in Sentry. +--- + +The Explore tab in Sentry offers multiple ways to search and investigate your application's data. You can look at your app's traces, metrics, profiles, and replays to get the information you need to debug issues more quickly and easily. + +## Learn More + + diff --git a/docs/product/metrics/img/Index.png b/docs/product/explore/metrics/img/Index.png similarity index 100% rename from docs/product/metrics/img/Index.png rename to docs/product/explore/metrics/img/Index.png diff --git a/docs/product/metrics/img/alerts-dashboards.png b/docs/product/explore/metrics/img/alerts-dashboards.png similarity index 100% rename from docs/product/metrics/img/alerts-dashboards.png rename to docs/product/explore/metrics/img/alerts-dashboards.png diff --git a/docs/product/metrics/img/cardinality.png b/docs/product/explore/metrics/img/cardinality.png similarity index 100% rename from docs/product/metrics/img/cardinality.png rename to docs/product/explore/metrics/img/cardinality.png diff --git a/docs/product/metrics/img/code-locations.png b/docs/product/explore/metrics/img/code-locations.png similarity index 100% rename from docs/product/metrics/img/code-locations.png rename to docs/product/explore/metrics/img/code-locations.png diff --git a/docs/product/metrics/img/enhance.png b/docs/product/explore/metrics/img/enhance.png similarity index 100% rename from docs/product/metrics/img/enhance.png rename to docs/product/explore/metrics/img/enhance.png diff --git a/docs/product/metrics/img/equations.png b/docs/product/explore/metrics/img/equations.png similarity index 100% rename from docs/product/metrics/img/equations.png rename to docs/product/explore/metrics/img/equations.png diff --git a/docs/product/metrics/img/metrics-explorer-query.png b/docs/product/explore/metrics/img/metrics-explorer-query.png similarity index 100% rename from docs/product/metrics/img/metrics-explorer-query.png rename to docs/product/explore/metrics/img/metrics-explorer-query.png diff --git a/docs/product/metrics/img/multiple-queries-2.png b/docs/product/explore/metrics/img/multiple-queries-2.png similarity index 100% rename from docs/product/metrics/img/multiple-queries-2.png rename to docs/product/explore/metrics/img/multiple-queries-2.png diff --git a/docs/product/metrics/img/multiple-queries.png b/docs/product/explore/metrics/img/multiple-queries.png similarity index 100% rename from docs/product/metrics/img/multiple-queries.png rename to docs/product/explore/metrics/img/multiple-queries.png diff --git a/docs/product/metrics/img/samples-table.png b/docs/product/explore/metrics/img/samples-table.png similarity index 100% rename from docs/product/metrics/img/samples-table.png rename to docs/product/explore/metrics/img/samples-table.png diff --git a/docs/product/metrics/index.mdx b/docs/product/explore/metrics/index.mdx similarity index 99% rename from docs/product/metrics/index.mdx rename to docs/product/explore/metrics/index.mdx index c7c64b9a79e58..0cb0deb9e4065 100644 --- a/docs/product/metrics/index.mdx +++ b/docs/product/explore/metrics/index.mdx @@ -1,6 +1,6 @@ --- title: "Metrics" -sidebar_order: 55 +sidebar_order: 40 description: "Metrics help you track and visualize the data points you care about, making it easier to monitor your application health and identify issues." --- diff --git a/docs/product/metrics/metrics-examples.mdx b/docs/product/explore/metrics/metrics-examples.mdx similarity index 88% rename from docs/product/metrics/metrics-examples.mdx rename to docs/product/explore/metrics/metrics-examples.mdx index 0db54fc693109..f36b4522b8b0b 100644 --- a/docs/product/metrics/metrics-examples.mdx +++ b/docs/product/explore/metrics/metrics-examples.mdx @@ -10,9 +10,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Count button clicks on subpages - + * Metric type: `counter` - * Example JavaScript code: + * Example JavaScript code: ```JavaScript Sentry.metrics.increment("button_click", 1, { @@ -23,9 +23,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Track number of user signups - + * Metric type: `counter` - * Example JavaScript code: + * Example JavaScript code: ```JavaScript Sentry.metrics.increment("signups", 1, { @@ -36,9 +36,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Measure UX improvement to signup form - + * Metric type: `distribution` - * Example JavaScript code: + * Example JavaScript code: ```JavaScript Sentry.metrics.distribution("login.time_to_finish_form", 14.3, { @@ -50,9 +50,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Track the loading time for a component - + * Metric type: `distribution` - * Example JavaScript code: + * Example JavaScript code: ```JavaScript Sentry.metrics.distribution("component_load_time", 15.0, { @@ -64,9 +64,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Track API request payloads - + * Metric type: `distribution` - * Example JavaScript code: + * Example JavaScript code: ```JavaScript Sentry.metrics.distribution("api_request_payload", 136.3, { @@ -78,9 +78,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Count concurrent users in application - + * Metric type: `gauge` - * Example JavaScript code: + * Example JavaScript code: ```JavaScript Sentry.metrics.gauge("concurrent_users", 10, { @@ -91,9 +91,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Track the number of items in a shopping cart - + * Metric type: `gauge` - * Example JavaScript code: + * Example JavaScript code: ```JavaScript Sentry.metrics.gauge("shopping_cart_item_count", itemCount, { @@ -104,9 +104,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Count the unique number of users on a page - + * Metric type: `set` - * Example JavaScript code: + * Example JavaScript code: ```JavaScript Sentry.metrics.set("user_view", "jane", { @@ -117,9 +117,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Count unique number of user sessions - + * Metric type: `set` - * Example JavaScript code: + * Example JavaScript code: ```JavaScript Sentry.metrics.set("unique_active_sessions", sessionId, { @@ -134,9 +134,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Count of API calls of a 3rd party API - + * Metric type: `counter` - * Example Python code: + * Example Python code: ```Python sentry_sdk.metrics.incr( @@ -149,9 +149,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Count of jobs executed per worker - + * Metric type: `counter` - * Example Python code: + * Example Python code: ```Python sentry_sdk.metrics.incr( @@ -164,9 +164,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Processing time for a task - + * Metric type: `distribution` - * Example Python code: + * Example Python code: ```Python sentry_sdk.metrics.distribution( @@ -180,9 +180,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Track ML model confidence during inference - + * Metric type: `distribution` - * Example Python code: + * Example Python code: ```Python sentry_sdk.metrics.distribution( @@ -196,9 +196,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Track CPU usage over time - + * Metric type: `gauge` - * Example Python code: + * Example Python code: ```Python sentry_sdk.metrics.gauge( @@ -211,9 +211,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Track cache hit ratio - + * Metric type: `gauge` - * Example Python code: + * Example Python code: ```Python sentry_sdk.metrics.gauge( @@ -226,9 +226,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Count unique server ids running a software version - + * Metric type: `set` - * Example Python code: + * Example Python code: ```Python sentry_sdk.metrics.set( @@ -241,9 +241,9 @@ If you're not sure where to start, here are a few examples of how you can use cu
Track number of unique DB queries executed - + * Metric type: `set` - * Example Python code: + * Example Python code: ```Python sentry_sdk.metrics.set( diff --git a/docs/product/metrics/metrics-explorer-page.mdx b/docs/product/explore/metrics/metrics-explorer-page.mdx similarity index 100% rename from docs/product/metrics/metrics-explorer-page.mdx rename to docs/product/explore/metrics/metrics-explorer-page.mdx diff --git a/docs/product/metrics/metrics-set-up.mdx b/docs/product/explore/metrics/metrics-set-up.mdx similarity index 100% rename from docs/product/metrics/metrics-set-up.mdx rename to docs/product/explore/metrics/metrics-set-up.mdx diff --git a/docs/product/profiling/differential-flamegraphs.mdx b/docs/product/explore/profiling/differential-flamegraphs.mdx similarity index 100% rename from docs/product/profiling/differential-flamegraphs.mdx rename to docs/product/explore/profiling/differential-flamegraphs.mdx diff --git a/docs/product/profiling/flame-charts-graphs.mdx b/docs/product/explore/profiling/flame-charts-graphs.mdx similarity index 100% rename from docs/product/profiling/flame-charts-graphs.mdx rename to docs/product/explore/profiling/flame-charts-graphs.mdx diff --git a/docs/product/profiling/getting-started.mdx b/docs/product/explore/profiling/getting-started.mdx similarity index 100% rename from docs/product/profiling/getting-started.mdx rename to docs/product/explore/profiling/getting-started.mdx diff --git a/docs/product/profiling/img/aggregated-flame-graph-view.png b/docs/product/explore/profiling/img/aggregated-flame-graph-view.png similarity index 100% rename from docs/product/profiling/img/aggregated-flame-graph-view.png rename to docs/product/explore/profiling/img/aggregated-flame-graph-view.png diff --git a/docs/product/profiling/img/call-stack-transaction.png b/docs/product/explore/profiling/img/call-stack-transaction.png similarity index 100% rename from docs/product/profiling/img/call-stack-transaction.png rename to docs/product/explore/profiling/img/call-stack-transaction.png diff --git a/docs/product/profiling/img/differential-flamegraph-inverted.png b/docs/product/explore/profiling/img/differential-flamegraph-inverted.png similarity index 100% rename from docs/product/profiling/img/differential-flamegraph-inverted.png rename to docs/product/explore/profiling/img/differential-flamegraph-inverted.png diff --git a/docs/product/profiling/img/differential-flamegraph-new.png b/docs/product/explore/profiling/img/differential-flamegraph-new.png similarity index 100% rename from docs/product/profiling/img/differential-flamegraph-new.png rename to docs/product/explore/profiling/img/differential-flamegraph-new.png diff --git a/docs/product/profiling/img/differential-flamegraph-regular.png b/docs/product/explore/profiling/img/differential-flamegraph-regular.png similarity index 100% rename from docs/product/profiling/img/differential-flamegraph-regular.png rename to docs/product/explore/profiling/img/differential-flamegraph-regular.png diff --git a/docs/product/profiling/img/differential-flamegraph-table.png b/docs/product/explore/profiling/img/differential-flamegraph-table.png similarity index 100% rename from docs/product/profiling/img/differential-flamegraph-table.png rename to docs/product/explore/profiling/img/differential-flamegraph-table.png diff --git a/docs/product/profiling/img/differential-flamegraph.png b/docs/product/explore/profiling/img/differential-flamegraph.png similarity index 100% rename from docs/product/profiling/img/differential-flamegraph.png rename to docs/product/explore/profiling/img/differential-flamegraph.png diff --git a/docs/product/profiling/img/fib-flame-chart.png b/docs/product/explore/profiling/img/fib-flame-chart.png similarity index 100% rename from docs/product/profiling/img/fib-flame-chart.png rename to docs/product/explore/profiling/img/fib-flame-chart.png diff --git a/docs/product/profiling/img/fib-flame-graph.png b/docs/product/explore/profiling/img/fib-flame-graph.png similarity index 100% rename from docs/product/profiling/img/fib-flame-graph.png rename to docs/product/explore/profiling/img/fib-flame-graph.png diff --git a/docs/product/profiling/img/flame-chart-hair.png b/docs/product/explore/profiling/img/flame-chart-hair.png similarity index 100% rename from docs/product/profiling/img/flame-chart-hair.png rename to docs/product/explore/profiling/img/flame-chart-hair.png diff --git a/docs/product/profiling/img/flame-chart-less-hair.png b/docs/product/explore/profiling/img/flame-chart-less-hair.png similarity index 100% rename from docs/product/profiling/img/flame-chart-less-hair.png rename to docs/product/explore/profiling/img/flame-chart-less-hair.png diff --git a/docs/product/profiling/img/flame-chart.png b/docs/product/explore/profiling/img/flame-chart.png similarity index 100% rename from docs/product/profiling/img/flame-chart.png rename to docs/product/explore/profiling/img/flame-chart.png diff --git a/docs/product/profiling/img/minimap.png b/docs/product/explore/profiling/img/minimap.png similarity index 100% rename from docs/product/profiling/img/minimap.png rename to docs/product/explore/profiling/img/minimap.png diff --git a/docs/product/profiling/img/new-transaction-profile-view.png b/docs/product/explore/profiling/img/new-transaction-profile-view.png similarity index 100% rename from docs/product/profiling/img/new-transaction-profile-view.png rename to docs/product/explore/profiling/img/new-transaction-profile-view.png diff --git a/docs/product/profiling/img/performance-page.png b/docs/product/explore/profiling/img/performance-page.png similarity index 100% rename from docs/product/profiling/img/performance-page.png rename to docs/product/explore/profiling/img/performance-page.png diff --git a/docs/product/profiling/img/profile-details-flame-chart.png b/docs/product/explore/profiling/img/profile-details-flame-chart.png similarity index 100% rename from docs/product/profiling/img/profile-details-flame-chart.png rename to docs/product/explore/profiling/img/profile-details-flame-chart.png diff --git a/docs/product/profiling/img/profile-flame-chart.png b/docs/product/explore/profiling/img/profile-flame-chart.png similarity index 100% rename from docs/product/profiling/img/profile-flame-chart.png rename to docs/product/explore/profiling/img/profile-flame-chart.png diff --git a/docs/product/profiling/img/profiling-details.png b/docs/product/explore/profiling/img/profiling-details.png similarity index 100% rename from docs/product/profiling/img/profiling-details.png rename to docs/product/explore/profiling/img/profiling-details.png diff --git a/docs/product/profiling/img/profiling-page-view.png b/docs/product/explore/profiling/img/profiling-page-view.png similarity index 100% rename from docs/product/profiling/img/profiling-page-view.png rename to docs/product/explore/profiling/img/profiling-page-view.png diff --git a/docs/product/profiling/img/search-bar.png b/docs/product/explore/profiling/img/search-bar.png similarity index 100% rename from docs/product/profiling/img/search-bar.png rename to docs/product/explore/profiling/img/search-bar.png diff --git a/docs/product/profiling/img/span-tree.png b/docs/product/explore/profiling/img/span-tree.png similarity index 100% rename from docs/product/profiling/img/span-tree.png rename to docs/product/explore/profiling/img/span-tree.png diff --git a/docs/product/profiling/img/table-view.gif b/docs/product/explore/profiling/img/table-view.gif similarity index 100% rename from docs/product/profiling/img/table-view.gif rename to docs/product/explore/profiling/img/table-view.gif diff --git a/docs/product/profiling/img/thread-selector.png b/docs/product/explore/profiling/img/thread-selector.png similarity index 100% rename from docs/product/profiling/img/thread-selector.png rename to docs/product/explore/profiling/img/thread-selector.png diff --git a/docs/product/profiling/img/transaction-environment-view.png b/docs/product/explore/profiling/img/transaction-environment-view.png similarity index 100% rename from docs/product/profiling/img/transaction-environment-view.png rename to docs/product/explore/profiling/img/transaction-environment-view.png diff --git a/docs/product/profiling/img/transaction-summary-page.png b/docs/product/explore/profiling/img/transaction-summary-page.png similarity index 100% rename from docs/product/profiling/img/transaction-summary-page.png rename to docs/product/explore/profiling/img/transaction-summary-page.png diff --git a/docs/product/profiling/img/waterfall-tree.png b/docs/product/explore/profiling/img/waterfall-tree.png similarity index 100% rename from docs/product/profiling/img/waterfall-tree.png rename to docs/product/explore/profiling/img/waterfall-tree.png diff --git a/docs/product/profiling/index.mdx b/docs/product/explore/profiling/index.mdx similarity index 92% rename from docs/product/profiling/index.mdx rename to docs/product/explore/profiling/index.mdx index 1705eac8c6326..fdc9820e1d352 100644 --- a/docs/product/profiling/index.mdx +++ b/docs/product/explore/profiling/index.mdx @@ -26,7 +26,7 @@ Sentry's profiling feature builds upon our established [Performance Monitoring]( Sentry profiling supports common platforms for both Mobile and Backend applications: -- [Mobile app profiling](/product/profiling/mobile-app-profiling/) makes it possible to collect **profiles from real devices in production**, providing a complete picture of how the app performs in a variety of environments. +- [Mobile app profiling](/product/explore/profiling/mobile-app-profiling/) makes it possible to collect **profiles from real devices in production**, providing a complete picture of how the app performs in a variety of environments. - Backend platform profiling makes it possible to easily target the essential code that yields the biggest improvements in backend throughput and resource utilization. ## Zooming In From Performance to Profiling @@ -39,7 +39,7 @@ This will take you to the **Transaction Summary** page where you'll see a list o ![Transaction Summary page](./img/transaction-summary-page.png) -Transaction events that have a profile contain a link in the "Profile" column which will take you to a flame graph with details about that event. Learn how to read [Flame Graphs and Aggregated Flame Graphs](/product/profiling/flame-charts-graphs). +Transaction events that have a profile contain a link in the "Profile" column which will take you to a flame graph with details about that event. Learn how to read [Flame Graphs and Aggregated Flame Graphs](/product/explore/profiling/flame-charts-graphs). ![Profile details page showing a flame graph](./img/profile-details-flame-chart.png) @@ -83,12 +83,12 @@ Below the general information is a list of regressions that Sentry may have dete There's also a list of the slowest functions which are consuming the most time in your application. These are good candidates for optimization. -On the left side of the page is an aggregate flamegraph as well as a digest of the slowest and most regressed functions. We recommend looking for wide frames that have no children as a starting point. This will allow you to identify frames that are often occupying the stack and make good candidates for optimization. Read the [Flame Graphs and Aggregated Flame Graphs](/product/profiling/flame-charts-graphs) docs if you'd like a deeper understanding of this data. +On the left side of the page is an aggregate flamegraph as well as a digest of the slowest and most regressed functions. We recommend looking for wide frames that have no children as a starting point. This will allow you to identify frames that are often occupying the stack and make good candidates for optimization. Read the [Flame Graphs and Aggregated Flame Graphs](/product/explore/profiling/flame-charts-graphs) docs if you'd like a deeper understanding of this data. An alternative way to visualize the flamegraph is by clicking on the "Call Tree" button which will render the flamegraph as an inverted call tree with the leftmost nodes first, which will then expand to their parent nodes. The sample column in the call tree represents the frequency with which Profiling collected stack samples where that function was on the stack. You can expand the tree by clicking on the caret before the function name. (Holding ⌘ at the same time will expand that entire branch all the way to the root.) ## Learn More -To learn more about profiling tools, read the docs about [Flame Graphs and Aggregated Flame Graphs](/product/profiling/flame-charts-graphs). +To learn more about profiling tools, read the docs about [Flame Graphs and Aggregated Flame Graphs](/product/explore/profiling/flame-charts-graphs). diff --git a/docs/product/profiling/mobile-app-profiling/img/flamechart-with-gpu-overlay.png b/docs/product/explore/profiling/mobile-app-profiling/img/flamechart-with-gpu-overlay.png similarity index 100% rename from docs/product/profiling/mobile-app-profiling/img/flamechart-with-gpu-overlay.png rename to docs/product/explore/profiling/mobile-app-profiling/img/flamechart-with-gpu-overlay.png diff --git a/docs/product/profiling/mobile-app-profiling/index.mdx b/docs/product/explore/profiling/mobile-app-profiling/index.mdx similarity index 100% rename from docs/product/profiling/mobile-app-profiling/index.mdx rename to docs/product/explore/profiling/mobile-app-profiling/index.mdx diff --git a/docs/product/profiling/mobile-app-profiling/metrics.mdx b/docs/product/explore/profiling/mobile-app-profiling/metrics.mdx similarity index 100% rename from docs/product/profiling/mobile-app-profiling/metrics.mdx rename to docs/product/explore/profiling/mobile-app-profiling/metrics.mdx diff --git a/docs/product/profiling/performance-overhead.mdx b/docs/product/explore/profiling/performance-overhead.mdx similarity index 100% rename from docs/product/profiling/performance-overhead.mdx rename to docs/product/explore/profiling/performance-overhead.mdx diff --git a/docs/product/profiling/profile-details.mdx b/docs/product/explore/profiling/profile-details.mdx similarity index 98% rename from docs/product/profiling/profile-details.mdx rename to docs/product/explore/profiling/profile-details.mdx index b96b9f19f4eec..d03a6cdc38479 100644 --- a/docs/product/profiling/profile-details.mdx +++ b/docs/product/explore/profiling/profile-details.mdx @@ -8,7 +8,7 @@ Profiling data can be used to gain insight into what methods and lines of your c ![Profiling details page](./img/profiling-details.png) -The main visualization on this page is a flame graph. Learn more about flame graphs in [Flame Graphs and Aggregated Flame Graphs](/product/profiling/flame-charts-graphs). +The main visualization on this page is a flame graph. Learn more about flame graphs in [Flame Graphs and Aggregated Flame Graphs](/product/explore/profiling/flame-charts-graphs). ## Thread Selector diff --git a/docs/product/session-replay/getting-started.mdx b/docs/product/explore/session-replay/getting-started.mdx similarity index 100% rename from docs/product/session-replay/getting-started.mdx rename to docs/product/explore/session-replay/getting-started.mdx diff --git a/docs/product/session-replay/img/replay-details-share.png b/docs/product/explore/session-replay/img/replay-details-share.png similarity index 100% rename from docs/product/session-replay/img/replay-details-share.png rename to docs/product/explore/session-replay/img/replay-details-share.png diff --git a/docs/product/session-replay/img/replay-details-tags.png b/docs/product/explore/session-replay/img/replay-details-tags.png similarity index 100% rename from docs/product/session-replay/img/replay-details-tags.png rename to docs/product/explore/session-replay/img/replay-details-tags.png diff --git a/docs/product/session-replay/img/replay-details.png b/docs/product/explore/session-replay/img/replay-details.png similarity index 100% rename from docs/product/session-replay/img/replay-details.png rename to docs/product/explore/session-replay/img/replay-details.png diff --git a/docs/product/session-replay/img/replay-index-filtering.png b/docs/product/explore/session-replay/img/replay-index-filtering.png similarity index 100% rename from docs/product/session-replay/img/replay-index-filtering.png rename to docs/product/explore/session-replay/img/replay-index-filtering.png diff --git a/docs/product/session-replay/img/session-replay-what-is-a-replay.png b/docs/product/explore/session-replay/img/session-replay-what-is-a-replay.png similarity index 100% rename from docs/product/session-replay/img/session-replay-what-is-a-replay.png rename to docs/product/explore/session-replay/img/session-replay-what-is-a-replay.png diff --git a/docs/product/session-replay/img/session-replay.png b/docs/product/explore/session-replay/img/session-replay.png similarity index 100% rename from docs/product/session-replay/img/session-replay.png rename to docs/product/explore/session-replay/img/session-replay.png diff --git a/docs/product/session-replay/index.mdx b/docs/product/explore/session-replay/index.mdx similarity index 91% rename from docs/product/session-replay/index.mdx rename to docs/product/explore/session-replay/index.mdx index 5e5bc96f04463..824a85d8f6388 100644 --- a/docs/product/session-replay/index.mdx +++ b/docs/product/explore/session-replay/index.mdx @@ -1,6 +1,6 @@ --- title: "Session Replay" -sidebar_order: 60 +sidebar_order: 70 description: "Use Session Replay to get video-like reproductions of user interactions to improve your website or app experience." --- @@ -8,7 +8,7 @@ description: "Use Session Replay to get video-like reproductions of user interac Session Replay allows you to see video-like reproductions of user sessions which can help you understand what happened before, during, and after an error or performance issue occurred. You'll be able to gain deeper debugging context into issues so that you can reproduce and resolve problems faster without the guesswork. As you play back each session, you'll be able to see every user interaction in relation to network requests, DOM events, and console messages. It’s effectively like having [DevTools](https://developer.chrome.com/docs/devtools/overview/) active in your production user sessions. -Replays are integrated with other parts of the Sentry product so you can see how the user experience is impacted by errors and slow transactions. You'll see session replays associated with error events on the [Issue Details](/product/issues/issue-details/) page, and those associated with slow transactions on the [Transaction Summary](/product/performance/transaction-summary/) page. For [backend error replays](/product/session-replay/getting-started#replays-for-backend-errors), any contributing backend errors will be included in the replay's timeline, [breadcrumbs](https://docs.sentry.io/product/issues/issue-details/breadcrumbs/), and errors. +Replays are integrated with other parts of the Sentry product so you can see how the user experience is impacted by errors and slow transactions. You'll see session replays associated with error events on the [Issue Details](/product/issues/issue-details/) page, and those associated with slow transactions on the [Transaction Summary](/product/performance/transaction-summary/) page. For [backend error replays](/product/explore/session-replay/getting-started#replays-for-backend-errors), any contributing backend errors will be included in the replay's timeline, [breadcrumbs](https://docs.sentry.io/product/issues/issue-details/breadcrumbs/), and errors. ![Session Replay User Interface](./img/session-replay.png) diff --git a/docs/product/session-replay/performance-overhead.mdx b/docs/product/explore/session-replay/performance-overhead.mdx similarity index 100% rename from docs/product/session-replay/performance-overhead.mdx rename to docs/product/explore/session-replay/performance-overhead.mdx diff --git a/docs/product/session-replay/replay-details.mdx b/docs/product/explore/session-replay/replay-details.mdx similarity index 100% rename from docs/product/session-replay/replay-details.mdx rename to docs/product/explore/session-replay/replay-details.mdx diff --git a/docs/product/session-replay/replay-page-and-filters.mdx b/docs/product/explore/session-replay/replay-page-and-filters.mdx similarity index 82% rename from docs/product/session-replay/replay-page-and-filters.mdx rename to docs/product/explore/session-replay/replay-page-and-filters.mdx index 8f780352a065d..7c658c607eda6 100644 --- a/docs/product/session-replay/replay-page-and-filters.mdx +++ b/docs/product/explore/session-replay/replay-page-and-filters.mdx @@ -22,10 +22,10 @@ By default, the IP address is used to identify each replay on this page. This ca Replays can appear on this page while they’re still in progress. You can’t delete in-progress replays. -Each replay will bring users to the [**Replay Details**](/product/session-replay/replay-details/) page. +Each replay will bring users to the [**Replay Details**](/product/explore/session-replay/replay-details/) page. ## Filtering Replays -All replays have built-in key fields, and may have [custom tags](/platforms/javascript/enriching-events/tags/) if you have them set up. The search bar operates similarly to the one in the Discover [Query Builder](/product/discover-queries/query-builder/#filter-by-search-conditions). Use it to enter these keys and assign them values. This will filter down your list of replays so you can quickly find the ones with the criteria you care about. For example, you can refine your replays search to a specific browser by using `browser.version:` as a key field and assigning the version as a value. For a list of all the built-in key fields/replay properties, check out our [Searchable Properties](/product/sentry-basics/search/searchable-properties/#replay-properties) documentation. +All replays have built-in key fields, and may have [custom tags](/platforms/javascript/enriching-events/tags/) if you have them set up. The search bar operates similarly to the one in the Discover [Query Builder](/product/explore/discover-queries/query-builder/#filter-by-search-conditions). Use it to enter these keys and assign them values. This will filter down your list of replays so you can quickly find the ones with the criteria you care about. For example, you can refine your replays search to a specific browser by using `browser.version:` as a key field and assigning the version as a value. For a list of all the built-in key fields/replay properties, check out our [Searchable Properties](/product/sentry-basics/search/searchable-properties/#replay-properties) documentation. ![Highlight the Search Filters input on the Session Replay Index Page](./img/replay-index-filtering.png) diff --git a/docs/product/index.mdx b/docs/product/index.mdx index a34da099e27f3..27a0632927704 100644 --- a/docs/product/index.mdx +++ b/docs/product/index.mdx @@ -18,7 +18,7 @@ Sentry's error monitoring capabilities make it possible to quickly get to the ro Sentry automatically captures unhandled exceptions (errors). It then groups similar errors into [issues](/product/issues/), making it possible to triage and manage them more efficiently. -- If you're monitoring a web project, you can [**replay**](/product/session-replay/) what the user experienced on your app and connect that error to the problematic line of code with [**source maps**](/product/sentry-basics/integrate-frontend/upload-source-maps/). +- If you're monitoring a web project, you can [**replay**](/product/explore/session-replay/) what the user experienced on your app and connect that error to the problematic line of code with [**source maps**](/product/sentry-basics/integrate-frontend/upload-source-maps/). - If you set up Sentry for both your frontend and backend, you'll be able to use [**distributed tracing**](/product/sentry-basics/concepts/tracing/distributed-tracing/) to see the sequence of events (both frontend and backend) that led up to the event of interest. - Additionally, you can set up [**integrations**](/organization/integrations/source-code-mgmt/) to link your source code so that Sentry can surface [**suspect commits**](/product/issues/suspect-commits/) and [**stack traces**](/organization/integrations/source-code-mgmt/github/#stack-trace-linking) to show the problematic line of code, as well as [**suggest assignees**](/organization/integrations/source-code-mgmt/github/#suspect-commits-and-suggested-assignees) for issues based on commit authors. @@ -27,7 +27,7 @@ Sentry automatically captures unhandled exceptions (errors). It then groups simi Our performance monitoring feature helps you track application performance, measure metrics like throughput and latency, and see the impact of errors across multiple services. - You can drill down into any slowdowns and optimize the performance of your code with [**distributed traces**](/product/sentry-basics/concepts/tracing/distributed-tracing/), which consist of transactions and spans and measure the performance of individual services and operations. This means you can easily [trace](/product/sentry-basics/concepts/tracing/trace-view/) slow-loading pages all the way back to poor-performing API calls. -- Sentry [**Profiling**](/product/profiling/) provides code-level insights into your application performance in production so you can find and fix the problematic line of code faster. It profiles code in every environment your application is running on so you can quickly see which functions are contributing to a slow span. +- Sentry [**Profiling**](/product/explore/profiling/) provides code-level insights into your application performance in production so you can find and fix the problematic line of code faster. It profiles code in every environment your application is running on so you can quickly see which functions are contributing to a slow span. - Sentry helps you discover and act on [**trends**](/product/performance/trends/) before they become a bigger problem by surfacing transactions whose performance has changed significantly over time. - Sentry provides insights to help you monitor your app's performance in various categories, including web vitals, mobile vitals, queries, HTTP requests, and more. You can drill into event samples to investigate variations in performance. @@ -50,7 +50,7 @@ Our [**LLM Monitoring**](/product/llm-monitoring/) feature gives you insights in ### Visibility Into Your Data Across Environments -[**Discover**](/product/discover-queries/) provides visibility into your data across environments by building upon and enriching your error data. You can [**query**](/product/discover-queries/query-builder/) and unlock insights into the health of your entire system and get answers to critical business questions — all in one place. You can also build your own [**dashboards**](/product/dashboards/) to help you monitor what's most important for your app. +[**Discover**](/product/explore/discover-queries/) provides visibility into your data across environments by building upon and enriching your error data. You can [**query**](/product/explore/discover-queries/query-builder/) and unlock insights into the health of your entire system and get answers to critical business questions — all in one place. You can also build your own [**dashboards**](/product/dashboards/) to help you monitor what's most important for your app. ### Code Coverage diff --git a/docs/product/issues/issue-details/index.mdx b/docs/product/issues/issue-details/index.mdx index ca060f9667f54..71d4869d6c112 100644 --- a/docs/product/issues/issue-details/index.mdx +++ b/docs/product/issues/issue-details/index.mdx @@ -25,7 +25,7 @@ This page displays the "Details" tab when it first opens, but several other tabs - **All Events** - A list of all the error events included in the issue. - **Merged Issues** - A list of error issues that have been merged with this one. - **Similar Issues** - A list of error issues that have a similar stack trace [that you can merge](/concepts/data-management/event-grouping/merging-issues/). -- **Replays** – A list of [replays](/product/session-replay/) tied to error events included in the issue. +- **Replays** – A list of [replays](/product/explore/session-replay/) tied to error events included in the issue. ## Issue Categories & Page Details @@ -105,7 +105,7 @@ It's the most important piece of information that the Sentry grouping algorithm You can set your own breadcrumbs to make them more useful for debugging. -If you’ve enabled [Session Replay](/product/session-replay/), you’ll see a replay preview under Breadcrumbs if there’s one associated with the event you’re viewing. Replays can be associated with both frontend and [backend errors](/product/session-replay/getting-started#replays-for-backend-errors) (as long as distrubted tracing is set up). Clicking on the replay preview will lead you to the [Replay Details](/product/session-replay/replay-details/) page. +If you’ve enabled [Session Replay](/product/explore/session-replay/), you’ll see a replay preview under Breadcrumbs if there’s one associated with the event you’re viewing. Replays can be associated with both frontend and [backend errors](/product/explore/session-replay/getting-started#replays-for-backend-errors) (as long as distrubted tracing is set up). Clicking on the replay preview will lead you to the [Replay Details](/product/explore/session-replay/replay-details/) page. ## Tags diff --git a/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx b/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx index b45cbdfde5363..648552f0fe2cc 100644 --- a/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx @@ -10,7 +10,7 @@ We can detect some specific causes for a main thread stall, like decoding [image ## Detection Criteria -[Profiling](/product/profiling/) must be enabled for Sentry to detect Frame Drop issues. Once set up, Sentry will look for profiles that record a frozen UI frame and then search for the most time-consuming application function call delaying the display link's next vsync. In a run of functions calling through without any self-time, the deepest call will be chosen. +[Profiling](/product/explore/profiling/) must be enabled for Sentry to detect Frame Drop issues. Once set up, Sentry will look for profiles that record a frozen UI frame and then search for the most time-consuming application function call delaying the display link's next vsync. In a run of functions calling through without any self-time, the deepest call will be chosen. diff --git a/docs/product/issues/issue-details/performance-issues/function-regressions.mdx b/docs/product/issues/issue-details/performance-issues/function-regressions.mdx index 7081cb5f9d992..db96f9acb1923 100644 --- a/docs/product/issues/issue-details/performance-issues/function-regressions.mdx +++ b/docs/product/issues/issue-details/performance-issues/function-regressions.mdx @@ -8,7 +8,7 @@ Function Regression issues capture a generic class of problems where the duratio ## Detection Criteria -Sentry can only detect Function Regression issues on projects that have [Profiling](/product/profiling) enabled. Sentry will periodically check the 95th percentile function duration of the most common application functions in your project. When a significant increase in the p95 value for function duration is detected and has been sustained for some time, a regression issue is created. +Sentry can only detect Function Regression issues on projects that have [Profiling](/product/explore/profiling) enabled. Sentry will periodically check the 95th percentile function duration of the most common application functions in your project. When a significant increase in the p95 value for function duration is detected and has been sustained for some time, a regression issue is created. ## Charts diff --git a/docs/product/issues/issue-details/performance-issues/image-decoding-main-thread/index.mdx b/docs/product/issues/issue-details/performance-issues/image-decoding-main-thread/index.mdx index 6066da9d85bfa..2cbab908cacde 100644 --- a/docs/product/issues/issue-details/performance-issues/image-decoding-main-thread/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/image-decoding-main-thread/index.mdx @@ -10,7 +10,7 @@ The process of decoding a compressed JPEG or PNG image into a bitmap (especially ## Detection Criteria -[Profiling](/product/profiling/) must be enabled for Sentry to detect Decoding on Main Thread issues. Sentry looks for functions related to image-decoding that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. +[Profiling](/product/explore/profiling/) must be enabled for Sentry to detect Decoding on Main Thread issues. Sentry looks for functions related to image-decoding that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. ## Function Evidence diff --git a/docs/product/issues/issue-details/performance-issues/json-decoding-main-thread/index.mdx b/docs/product/issues/issue-details/performance-issues/json-decoding-main-thread/index.mdx index 09a05fa90756d..fb4384951e1ff 100644 --- a/docs/product/issues/issue-details/performance-issues/json-decoding-main-thread/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/json-decoding-main-thread/index.mdx @@ -12,7 +12,7 @@ Decoding a JSON blob into a data structure can be a long running operation, espe ## Detection Criteria -[Profiling](/product/profiling/) must be enabled for Sentry to detect JSON Decoding on Main Thread issues. Sentry looks for functions related to JSON decoding that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. +[Profiling](/product/explore/profiling/) must be enabled for Sentry to detect JSON Decoding on Main Thread issues. Sentry looks for functions related to JSON decoding that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. ## Function Evidence diff --git a/docs/product/issues/issue-details/performance-issues/regex-main-thread/index.mdx b/docs/product/issues/issue-details/performance-issues/regex-main-thread/index.mdx index b9e675ed2909e..d1fdfec67e641 100644 --- a/docs/product/issues/issue-details/performance-issues/regex-main-thread/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/regex-main-thread/index.mdx @@ -10,7 +10,7 @@ Evaluating matches between strings and regular expressions (regex) can be long-r ## Detection Criteria -[Profiling](/product/profiling/) must be enabled for Sentry to detect Regex on Main Thread issues. Sentry looks for functions related to regular expressions that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. +[Profiling](/product/explore/profiling/) must be enabled for Sentry to detect Regex on Main Thread issues. Sentry looks for functions related to regular expressions that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. ## Function Evidence diff --git a/docs/product/issues/issue-details/replay-issues/index.mdx b/docs/product/issues/issue-details/replay-issues/index.mdx index 98b13e6e5b581..26fb2b6600a92 100644 --- a/docs/product/issues/issue-details/replay-issues/index.mdx +++ b/docs/product/issues/issue-details/replay-issues/index.mdx @@ -4,7 +4,7 @@ sidebar_order: 30 description: "Learn about Session Replay rage click issues." --- -If you've enabled [Session Replay](/product/session-replay/), you'll be able to see rage click issues on the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues/) page in Sentry. Rage clicks are a series of consecutive clicks on the same unresponsive element. They are a sure sign of user frustration and most likely deserve your attention. +If you've enabled [Session Replay](/product/explore/session-replay/), you'll be able to see rage click issues on the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues/) page in Sentry. Rage clicks are a series of consecutive clicks on the same unresponsive element. They are a sure sign of user frustration and most likely deserve your attention. ![Rage click issue](./img/Rage-click-issue-in-issue-stream.png) @@ -12,7 +12,7 @@ If you've enabled [Session Replay](/product/session-replay/), you'll be able to In order to see rage clicks in your issue stream on the **Issues** page, your organization needs to: -- Be sending [session replay events](/product/session-replay/getting-started/) +- Be sending [session replay events](/product/explore/session-replay/getting-started/) - Enable the JavaScript SDK (or framework-specific bundle), version 7.60.1 or higher diff --git a/docs/product/performance/filters-display/index.mdx b/docs/product/performance/filters-display/index.mdx index 67c340f6f6910..4eb8588f9fd54 100644 --- a/docs/product/performance/filters-display/index.mdx +++ b/docs/product/performance/filters-display/index.mdx @@ -51,7 +51,7 @@ When you begin typing, a list of transaction names that match your search appear ### Search Condition Filters -In the transaction summary, the search bar operates similarly to the one in the Discover [Query Builder](/product/discover-queries/query-builder/#filter-by-search-conditions). For example, you can refine your transaction search to a specific release by using `release:` as a key field and assigning the version as a value. +In the transaction summary, the search bar operates similarly to the one in the Discover [Query Builder](/product/explore/discover-queries/query-builder/#filter-by-search-conditions). For example, you can refine your transaction search to a specific release by using `release:` as a key field and assigning the version as a value. ## Widgets diff --git a/docs/product/performance/getting-started.mdx b/docs/product/performance/getting-started.mdx index 26ee8631596a9..479f42238a0bc 100644 --- a/docs/product/performance/getting-started.mdx +++ b/docs/product/performance/getting-started.mdx @@ -4,7 +4,7 @@ sidebar_order: 1 description: "Get started with Sentry's Performance Monitoring, which allows you to see macro-level metrics to micro-level spans, cross-reference transactions with related issues, and customize queries." --- -If you don't already have performance monitoring enabled, use the links for supported SDKs below to quickly set up access to our [Performance Monitoring](/product/performance/) features. Performance Monitoring helps you see everything from macro-level [metrics](/product/performance/metrics/) to micro-level [spans](/concepts/key-terms/tracing/trace-view/#product-walkthrough-trace-view-page), and you'll be able to cross-reference [transactions with related issues](/product/performance/transaction-summary/), customize [queries](/product/discover-queries/query-builder/) based on your personal needs, and substantially more. +If you don't already have performance monitoring enabled, use the links for supported SDKs below to quickly set up access to our [Performance Monitoring](/product/performance/) features. Performance Monitoring helps you see everything from macro-level [metrics](/product/performance/metrics/) to micro-level [spans](/concepts/key-terms/tracing/trace-view/#product-walkthrough-trace-view-page), and you'll be able to cross-reference [transactions with related issues](/product/performance/transaction-summary/), customize [queries](/product/explore/discover-queries/query-builder/) based on your personal needs, and substantially more. ## Supported SDKs diff --git a/docs/product/performance/metrics.mdx b/docs/product/performance/metrics.mdx index cca9a8051b761..e3a842efde5f7 100644 --- a/docs/product/performance/metrics.mdx +++ b/docs/product/performance/metrics.mdx @@ -6,11 +6,11 @@ description: "Learn more about Sentry's Performance metrics such as Apdex, failu -If you are looking to try out custom metrics (currently in beta), you can learn more [here](https://docs.sentry.io/product/metrics/) +If you are looking to try out custom metrics (currently in beta), you can learn more [here](/product/explore/metrics/) -Metrics provide insight about how users are experiencing your application. In [Performance](/product/performance/), we'll set you up with a few of the basic metrics to get you started. For further customizations on target thresholds, feel free to build out a query using the Discover [Query Builder](/product/discover-queries/query-builder/). By identifying useful thresholds to measure your application, you have a quantifiable measurement of your application's health. This means you can more easily identify when errors occur or if performance issues are emerging. +Metrics provide insight about how users are experiencing your application. In [Performance](/product/performance/), we'll set you up with a few of the basic metrics to get you started. For further customizations on target thresholds, feel free to build out a query using the Discover [Query Builder](/product/explore/discover-queries/query-builder/). By identifying useful thresholds to measure your application, you have a quantifiable measurement of your application's health. This means you can more easily identify when errors occur or if performance issues are emerging. ## Apdex @@ -89,7 +89,7 @@ You can set satisfactory thresholds for each project with [custom thresholds](#c -User Misery is calculated using a probability distribution. This prevents false positives and ensures reasonable values for datasets with low event volume. You can view the underlying data by querying for the [`count_miserable()` function](/product/discover-queries/query-builder/#stacking-functions). +User Misery is calculated using a probability distribution. This prevents false positives and ensures reasonable values for datasets with low event volume. You can view the underlying data by querying for the [`count_miserable()` function](/product/explore/discover-queries/query-builder/#stacking-functions). diff --git a/docs/product/performance/mobile-vitals/app-starts.mdx b/docs/product/performance/mobile-vitals/app-starts.mdx index cb73c4593513d..346e14ea7efb9 100644 --- a/docs/product/performance/mobile-vitals/app-starts.mdx +++ b/docs/product/performance/mobile-vitals/app-starts.mdx @@ -104,4 +104,4 @@ Sentry automatically identifies sample events to help you investigate performanc You can use the sample list to drill down to and compare fast, average, and slow events of interest within a given screen. -Clicking on a sample event will take you into either the query’s span details within the span waterfall of the [Trace View page](/concepts/key-terms/tracing/trace-view/#product-walkthrough-trace-view-page) or the profile icon to see the [flamegraph](/product/profiling/flame-charts-graphs/) for the event. To get different event samples, click the "Try Different Samples" button. +Clicking on a sample event will take you into either the query’s span details within the span waterfall of the [Trace View page](/concepts/key-terms/tracing/trace-view/#product-walkthrough-trace-view-page) or the profile icon to see the [flamegraph](/product/explore/profiling/flame-charts-graphs/) for the event. To get different event samples, click the "Try Different Samples" button. diff --git a/docs/product/performance/mobile-vitals/screen-loads.mdx b/docs/product/performance/mobile-vitals/screen-loads.mdx index af934f3672ef2..4e4eaedc9e0a3 100644 --- a/docs/product/performance/mobile-vitals/screen-loads.mdx +++ b/docs/product/performance/mobile-vitals/screen-loads.mdx @@ -88,4 +88,4 @@ Sentry automatically identifies sample events to help you investigate performanc You can use the sample list to drill down to and compare fast, average, and slow events of interest within a given screen. -Clicking on a sample event will take you into either the query's span details within the span waterfall of the [Trace Details page](/concepts/key-terms/tracing/trace-view/) or the profile icon to see the [flamegraph](/product/profiling/flame-charts-graphs/) for the event. To get different event samples, click the "Try Different Samples" button. +Clicking on a sample event will take you into either the query's span details within the span waterfall of the [Trace Details page](/concepts/key-terms/tracing/trace-view/) or the profile icon to see the [flamegraph](/product/explore/profiling/flame-charts-graphs/) for the event. To get different event samples, click the "Try Different Samples" button. diff --git a/docs/product/performance/retention-priorities/index.mdx b/docs/product/performance/retention-priorities/index.mdx index 6c9c75970a5a9..feebd8e11b94b 100644 --- a/docs/product/performance/retention-priorities/index.mdx +++ b/docs/product/performance/retention-priorities/index.mdx @@ -80,7 +80,7 @@ Investigation sampling rules only apply to transactions and don't guarantee that #### Creating a New Investigation Rule -When you perform a query on transactions either in [Discover](/product/discover-queries/) or in [Transaction Summary](/product/performance/transaction-summary/) and receive fewer than 5 samples, you can click "Get Samples" to create a new investigation rule to retain more samples of transactions for the respective query. +When you perform a query on transactions either in [Discover](/product/explore/discover-queries/) or in [Transaction Summary](/product/performance/transaction-summary/) and receive fewer than 5 samples, you can click "Get Samples" to create a new investigation rule to retain more samples of transactions for the respective query. ![Investigation Mode in Discover](./img/investigation-bias-discover.png) diff --git a/docs/product/performance/transaction-summary.mdx b/docs/product/performance/transaction-summary.mdx index 9bf14e97cf891..5d3c03a5d577b 100644 --- a/docs/product/performance/transaction-summary.mdx +++ b/docs/product/performance/transaction-summary.mdx @@ -53,7 +53,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 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/explore/discover-queries/query-builder/). @@ -99,7 +99,7 @@ By default, outliers will be excluded from the histograms to provide a more info The vertical marker for each Web Vital is the 75th percentile of the observed data points. In other words, 25% of the recorded values exceed that amount. -If you notice a region of interest on any of the histograms, click and drag over the area to zoom in for a more detailed view. You may also want to see more information related to the transactions in the histograms. Click "Open in Discover" beneath the Web Vital of choice to build a custom query for further investigation. For more details, see the full documentation for the Discover [Query Builder](/product/discover-queries/query-builder/). +If you notice a region of interest on any of the histograms, click and drag over the area to zoom in for a more detailed view. You may also want to see more information related to the transactions in the histograms. Click "Open in Discover" beneath the Web Vital of choice to build a custom query for further investigation. For more details, see the full documentation for the Discover [Query Builder](/product/explore/discover-queries/query-builder/). If you wish to see all of the data available, open the dropdown and click "View All". You will likely see extreme outliers when you click "View All". You can click and drag over an area to zoom in for a more detailed view. @@ -157,7 +157,7 @@ Spans with the same operation and description are grouped together into a single ### Replays -The Replays tab displays a list of replays where the transaction you’re viewing had occurred. Go directly to [Replay Details](/product/session-replay/replay-details/) for any replay and see how a slow transaction impacted the user experience. Note: you must have [Session Replay](/product/session-replay/) enabled to see this tab. +The Replays tab displays a list of replays where the transaction you’re viewing had occurred. Go directly to [Replay Details](/product/explore/session-replay/replay-details/) for any replay and see how a slow transaction impacted the user experience. Note: you must have [Session Replay](/product/explore/session-replay/) enabled to see this tab. ## Additional Actions diff --git a/docs/product/performance/web-vitals/index.mdx b/docs/product/performance/web-vitals/index.mdx index 33dcd6fe3e545..d5ea211b7b67f 100644 --- a/docs/product/performance/web-vitals/index.mdx +++ b/docs/product/performance/web-vitals/index.mdx @@ -5,7 +5,7 @@ description: "Understand your application's performance score and how each web v --- -On March 12, 2024, Google replaced [First Input Display (FID)](/product/performance/web-vitals/web-vitals-concepts/#first-input-delay-fid) with [Interaction to Next Paint (INP)](/product/performance/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) as a Core Web Vital. To begin collecting INP measurements, make sure your Javascript SDK version is [7.104.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.104.0) or higher and that the option [`enableInp`](/platforms/javascript/performance/instrumentation/automatic-instrumentation/#enableinp) is on. FID measurements are no longer shown in the **Web Vitals** page, but can still be accessed in [Discover](/product/discover-queries). You may see changes to your performance score during this transition. +On March 12, 2024, Google replaced [First Input Display (FID)](/product/performance/web-vitals/web-vitals-concepts/#first-input-delay-fid) with [Interaction to Next Paint (INP)](/product/performance/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) as a Core Web Vital. To begin collecting INP measurements, make sure your Javascript SDK version is [7.104.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.104.0) or higher and that the option [`enableInp`](/platforms/javascript/performance/instrumentation/automatic-instrumentation/#enableinp) is on. FID measurements are no longer shown in the **Web Vitals** page, but can still be accessed in [Discover](/product/explore/discover-queries). You may see changes to your performance score during this transition. Web vitals are a set of metrics that measure the quality of the user experience on a web page. To learn more about these metrics, see [Web Vitals Concepts](/product/performance/web-vitals/web-vitals-concepts/). @@ -42,7 +42,7 @@ The **Web Vitals** page only displays data from your application's initial page ## Page Overview -From the table in **Web Vitals** or a Web Vital Summary panel, click on a page to open its **Page Overview**. Here, you can see a summary of that single page's Web Vitals. In **Page Overview**, you can further drill down to a specific page load sample [Event](/concepts/key-terms/tracing/trace-view/), [Interaction](/product/performance/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp), [Replay](/product/session-replay/), or [Profile](/product/profiling/). +From the table in **Web Vitals** or a Web Vital Summary panel, click on a page to open its **Page Overview**. Here, you can see a summary of that single page's Web Vitals. In **Page Overview**, you can further drill down to a specific page load sample [Event](/concepts/key-terms/tracing/trace-view/), [Interaction](/product/performance/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp), [Replay](/product/explore/session-replay/), or [Profile](/product/explore/profiling/). The **Page Overview** page displays a "Page Loads" chart in the right sidebar of the page. A mini **Aggregate Span Waterfall** is also displayed in the right sidebar, which shows you common span paths that your application's page may take. Click the "View Full Waterfall" button or the "Aggregate Spans" tab at the top of the page to see the full **Aggregate Span Waterfall**. @@ -60,7 +60,7 @@ The **Page Overview** page displays a "Page Loads" chart in the right sidebar of ### Samples List -At the center of the **Page Overview**, Web Vital p75 values and scores are displayed. Clicking a Web Vital score will open a slideout panel containing a variety of **Page Load** samples with good to poor scores. Each sample contains an **Event ID** that can be clicked to open the [Trace Details](/concepts/key-terms/tracing/trace-view/#product-walkthrough-trace-details-page) page for further investigation. If there is a [Replay](/product/session-replay/) or [Profile](/product/profiling/) associated with the sample page load, links will be included in the associated table columns. +At the center of the **Page Overview**, Web Vital p75 values and scores are displayed. Clicking a Web Vital score will open a slideout panel containing a variety of **Page Load** samples with good to poor scores. Each sample contains an **Event ID** that can be clicked to open the [Trace Details](/concepts/key-terms/tracing/trace-view/#product-walkthrough-trace-details-page) page for further investigation. If there is a [Replay](/product/explore/session-replay/) or [Profile](/product/explore/profiling/) associated with the sample page load, links will be included in the associated table columns.