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
Follow up to #14096.
- Makes the entire `mdx.ts` and accompanying modules async
- Limits concurrency in `mdx.ts` async ops (otherwise we crash Vercel
Functions / AWS Lambda) (check
https://sentry-docs-git-byk-cimdx-cache.sentry.dev/platform-redirect/ --
should not crash)
- Adds compression to caches (as Vercel complained about the function
size)
- Removes the `<script>` blocks from the HTML for cache key calculation
and faster `md` generation. Script blocks are already ignored and they
are not stable across builds even when nothing changes, causing cache
misses.
Cuts down build times from ~21-22 minutes to ~13-14 minutes.
Copy file name to clipboardExpand all lines: docs/product/explore/session-replay/web/index.mdx
-2Lines changed: 0 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,6 @@ sidebar_order: 10
4
4
description: "Learn about Session Replay and its video-like reproductions of user interactions, which can help you see when users are frustrated and build a better web experience."
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.
10
8
11
9
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/insights/overview/transaction-summary/) page. For [backend error replays](/product/explore/session-replay/web/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.
Copy file name to clipboardExpand all lines: docs/product/sentry-basics/performance-monitoring.mdx
-2Lines changed: 0 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,6 @@ sidebar_order: 1
4
4
description: "Understand and monitor how your application performs in production. Track key metrics, analyze bottlenecks, and resolve performance issues with distributed tracing, detailed transaction data, and automated issue detection."
5
5
---
6
6
7
-
<Includename="performance-moving.mdx" />
8
-
9
7
In many tools, Performance Monitoring is just about tracking a few key metrics on your web pages. Sentry takes a different approach. By setting up [Tracing](/concepts/key-terms/tracing/), Sentry captures detailed performance data for every transaction in your entire application stack and automatically presents it in a variety of easy-to-use but powerful features so you can rapidly identify and resolve performance issues as they happen - all in one place.
0 commit comments