You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/concepts/key-terms/key-terms.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ Each of these key features in [sentry.io](https://sentry.io) is represented by a
50
50
51
51
-**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/).
52
52
53
-
-**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/).
53
+
-**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/).
54
54
55
55
-**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/).
Copy file name to clipboardExpand all lines: docs/concepts/key-terms/tracing/distributed-tracing.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -243,4 +243,4 @@ Put simply: as a result of this head-based approach, where the decision is made
243
243
244
244
## Viewing Trace Data
245
245
246
-
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.
246
+
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.
Copy file name to clipboardExpand all lines: docs/concepts/search/index.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ Here are some examples of valid comparison operator searches:
50
50
51
51
<Note>
52
52
53
-
`OR` and `AND` search conditions are only available for [Discover](/product/discover-queries/), [Performance](/product/performance/), and [Metric Alerts](/product/alerts-notifications/metric-alerts/).
53
+
`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/).
Copy file name to clipboardExpand all lines: docs/concepts/search/searchable-properties/session-replay.mdx
+5-5
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: "Learn more about searchable session replay properties."
4
4
sidebar_order: 30
5
5
---
6
6
7
-
[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.
7
+
[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.
8
8
9
9
You can search by session replay properties on the **Replay** page.
10
10
@@ -102,7 +102,7 @@ The `title` of an element that was clicked. For example, `Save this comment` wou
102
102
103
103
### `count_dead_clicks`
104
104
105
-
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.
105
+
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.
106
106
107
107
-**Type:** number
108
108
@@ -114,7 +114,7 @@ The number of errors within a replay.
114
114
115
115
### `count_rage_clicks`
116
116
117
-
The number of [rage clicks](<https://docs.sentry.io/product/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>) within a replay.
117
+
The number of [rage clicks](<https://docs.sentry.io/product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>) within a replay.
118
118
119
119
-**Type:** number
120
120
@@ -132,7 +132,7 @@ The number of URLs that the user visited during a replay recording.
132
132
133
133
### `dead.selector`
134
134
135
-
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 `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
135
+
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 `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
136
136
137
137
-**Type:** string
138
138
@@ -216,7 +216,7 @@ The id of the project.
216
216
217
217
### `rage.selector`
218
218
219
-
Similar to the `click.selector` search property, but only queries on [rage clicks](<https://docs.sentry.io/product/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
219
+
Similar to the `click.selector` search property, but only queries on [rage clicks](<https://docs.sentry.io/product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
Copy file name to clipboardExpand all lines: docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ With this feature, the SDK differentiates between four different app start types
105
105
- **Prewarmed cold start**
106
106
- **Prewarmed warm start**
107
107
108
-
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`.
108
+
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`.
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.
9
+
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.
[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.
27
+
[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.
28
28
29
29
Read more about <PlatformLinkto='/profiling'>setting up Profiling</PlatformLink>.
Copy file name to clipboardExpand all lines: docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,6 @@ supported:
24
24
25
25
_Import name: `Sentry.nodeProfilingIntegration`_
26
26
27
-
[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.
27
+
[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.
28
28
29
29
Read more about <PlatformLinkto='/profiling'>setting up Profiling</PlatformLink>.
Copy file name to clipboardExpand all lines: docs/platforms/javascript/common/configuration/integrations/replay.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,6 @@ notSupported:
24
24
25
25
_Import name: `Sentry.replayIntegration`_
26
26
27
-
[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.
27
+
[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.
28
28
29
29
Read more about [setting up Session Replay](./../../../session-replay/).
[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.
24
+
[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.
25
25
26
26
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 <PlatformLinkto="/session-replay/privacy">Session Replay Privacy</PlatformLink>.
Copy file name to clipboardExpand all lines: docs/platforms/javascript/common/session-replay/troubleshooting.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,7 @@ Sentry.replayIntegration({
106
106
107
107
<Expandabletitle='I see the message: "A large number of mutations was detected (N). This can slow down the Replay SDK and impact your customers."'>
108
108
109
-
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.
109
+
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.
110
110
111
111
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 <PlatformLinkto="/session-replay/configuration/#mutation-limits">configuration</PlatformLink> that allows you to configure the limits before recording stops.
Copy file name to clipboardExpand all lines: docs/platforms/php/common/profiling/index.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Profiling for PHP is supported with Sentry PHP SDK version `3.15.0` and above.
10
10
11
11
</Note>
12
12
13
-
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.
13
+
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.
14
14
15
15
Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer).
16
16
The Excimer PHP extension supports PHP 7.2 and up.
Copy file name to clipboardExpand all lines: docs/platforms/php/guides/laravel/profiling/index.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Profiling for PHP is supported with Sentry Laravel SDK version `3.3.0` and above
10
10
11
11
</Note>
12
12
13
-
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.
13
+
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.
14
14
15
15
Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer).
16
16
The Excimer PHP extension supports PHP 7.2 and up.
Copy file name to clipboardExpand all lines: docs/platforms/php/guides/symfony/profiling/index.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Profiling for PHP is supported with Sentry Symfony SDK version `4.7.0` and above
10
10
11
11
</Note>
12
12
13
-
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.
13
+
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.
14
14
15
15
Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer).
16
16
The Excimer PHP extension supports PHP 7.2 and up.
Copy file name to clipboardExpand all lines: docs/platforms/react-native/profiling/troubleshooting/index.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ If you don't see any profiling data in [sentry.io](https://sentry.io), you can t
13
13
14
14
### Limitations
15
15
16
-
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
16
+
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
17
17
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.
18
18
19
19
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).
Copy file name to clipboardExpand all lines: docs/pricing/index.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ Performance Units can be used towards multiple Performance event types, dependin
54
54
| Event Type | Unit Value ||
55
55
|---|---|---|
56
56
| Transactions | 1 Unit | Sent by SDKs with only [Tracing](/product/sentry-basics/tracing/) enabled |
57
-
| Transactions with Profiling | 1.3 Units | Sent by SDKs with both [Tracing](/product/sentry-basics/tracing/) & [Profiling](/product/profiling/) enabled |
57
+
| Transactions with Profiling | 1.3 Units | Sent by SDKs with both [Tracing](/product/sentry-basics/tracing/) & [Profiling](/product/explore/profiling/) enabled |
58
58
59
59
| Total Performance Unit Volume | Team Prepaid | Team On-Demand | Business Prepaid | Business On-Demand |
0 commit comments