Skip to content

Commit 47534e2

Browse files
committed
de-dupe "Replays for Backend Errors" section and include tracePropagationTargets examples
1 parent d05cac2 commit 47534e2

File tree

4 files changed

+46
-30
lines changed

4 files changed

+46
-30
lines changed

docs/product/explore/session-replay/mobile/index.mdx

Lines changed: 26 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -31,22 +31,36 @@ We recommend updating to the latest version, but the minimum versions supported
3131
- [React Native](/platforms/react-native/session-replay/), [6.5.0](https://github.com/getsentry/sentry-react-native/releases)
3232
- [Flutter](/platforms/dart/guides/flutter/session-replay/), [8.12.0](https://github.com/getsentry/sentry-dart/releases)
3333

34-
## Replays for Backend Errors
34+
<Include name="session-replay-for-backend-errors.mdx" />
3535

36-
Replays are integrated with Sentry's tracing data model, enabling you to see replays associated with backend errors. For these replays, you can view backend errors in the Timeline, the Breadcrumbs and Errors tabs, and other places when you go to the **Replay Details** view. You'll also see a Replays tab and replay previews in the **Issue Details** page for any backend error that has a linked replay.
36+
Make sure you've set up [trace propagation](/product/sentry-basics/concepts/tracing/#trace-propagation) in your backend projects. For example:
3737

38-
To see replays for backend errors, you need to have Sentry set up for both your frontend and backend, along with [distributed tracing](/product/sentry-basics/concepts/tracing/). This provides end-to-end data connectivity on your APIs, allowing Sentry to link replays to backend endpoints. Make sure you've set up trace propagation in your backend projects. For example:
38+
```swift {tabTitle:Swift}
39+
import Sentry
3940

40-
Currently, replays for backend errors are supported for the following SDK versions or newer:
41+
SentrySDK.start { options in
42+
options.dsn = "___PUBLIC_DSN___"
43+
options.tracePropagationTargets = ["MyAppDomain.com"]
44+
}
45+
```
4146

42-
- JavaScript (or related framework) [7.51.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.51.0)
43-
- Python [1.26.0](https://github.com/getsentry/sentry-python/releases/tag/1.26.0)
44-
- Node [7.48.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.48.0)
45-
- PHP [3.18.0](https://github.com/getsentry/sentry-php/releases/tag/3.18.0)
46-
- .NET [3.31.0](https://github.com/getsentry/sentry-dotnet/releases/tag/3.31.0)
47-
- Java [6.17.0](https://github.com/getsentry/sentry-java/releases/tag/6.17.0)
48-
- Ruby [5.9.0](https://github.com/getsentry/sentry-ruby/releases/tag/5.9.0)
49-
- Go [0.21.0](https://github.com/getsentry/sentry-go/releases/tag/v0.21.0)
47+
```objc {tabTitle:Objective-C}
48+
@import Sentry;
49+
50+
[SentrySDK startWithConfigureOptions:^(SentryOptions *options) {
51+
options.dsn = @"___PUBLIC_DSN___";
52+
options.tracePropagationTargets = @[@"MyAppDomain.com"]
53+
}];
54+
```
55+
56+
```javascript {tabTitle:JavaScript}
57+
Sentry.init({
58+
dsn: "___PUBLIC_DSN___";
59+
tracePropagationTargets: ["https://myproject.org", /^\/api\//],
60+
});
61+
```
62+
63+
<Include name="session-replay-for-backend-support.mdx" />
5064

5165
## Frequently Asked Questions
5266

docs/product/explore/session-replay/web/index.mdx

Lines changed: 5 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -63,28 +63,15 @@ The Sentry SDK that records the replay runs on the client's browser, and it’s
6363
- [SvelteKit](/platforms/javascript/guides/sveltekit/session-replay/)
6464
- [Vue](/platforms/javascript/guides/vue/session-replay/)
6565

66-
## Replays for Backend Errors
66+
<Include name="session-replay-for-backend-errors.mdx" />
6767

68-
Replays are integrated with Sentry's tracing data model, enabling you to see replays associated with backend errors. For these replays, you can view backend errors in the Timeline, Breadcrumbs and Errors tabs, and other places when you go to the **Replay Details** view. You'll also see a Replays tab and replay previews in the **Issue Details** page for any backend error that has a linked replay.
69-
70-
To see replays for backend errors, you need to have Sentry set up for both your frontend and backend, along with [distributed tracing](/product/sentry-basics/concepts/tracing/). This provides end-to-end data connectivity on your APIs, allowing Sentry to link replays to backend endpoints. Make sure you've set up trace propagation in your backend projects. For example:
68+
Make sure you've set up [trace propagation](/product/sentry-basics/concepts/tracing/#trace-propagation) in your backend projects. For example:
7169

7270
```javascript
7371
Sentry.init({
74-
tracePropagationTargets: [
75-
"third-party-site.com",
76-
/^https:\/\/yourserver\.io\/api/,
77-
],
72+
dsn: "___PUBLIC_DSN___";
73+
tracePropagationTargets: ["https://myproject.org", /^\/api\//],
7874
});
7975
```
8076

81-
Currently, replays for backend errors are supported for the following SDK versions or newer:
82-
83-
- JavaScript (or related framework) [7.51.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.51.0)
84-
- Python [1.26.0](https://github.com/getsentry/sentry-python/releases/tag/1.26.0)
85-
- Node [7.48.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.48.0)
86-
- PHP [3.18.0](https://github.com/getsentry/sentry-php/releases/tag/3.18.0)
87-
- .NET [3.31.0](https://github.com/getsentry/sentry-dotnet/releases/tag/3.31.0)
88-
- Java [6.17.0](https://github.com/getsentry/sentry-java/releases/tag/6.17.0)
89-
- Ruby [5.9.0](https://github.com/getsentry/sentry-ruby/releases/tag/5.9.0)
90-
- Go [0.21.0](https://github.com/getsentry/sentry-go/releases/tag/v0.21.0)
77+
<Include name="session-replay-for-backend-support.mdx" />
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
## Replays for Backend Errors
2+
3+
Replays are integrated with Sentry's tracing data model, enabling you to see replays associated with backend errors. For these replays, you can view backend errors in the Timeline, the Breadcrumbs and Errors tabs, and other places when you go to the **Replay Details** view. You'll also see a Replays tab and replay previews in the **Issue Details** page for any backend error that has a linked replay.
4+
5+
To see replays for backend errors, you need to have Sentry set up for both your frontend and backend, along with [distributed tracing](/product/sentry-basics/concepts/tracing/). This provides end-to-end data connectivity on your APIs, allowing Sentry to link replays to backend endpoints.
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
Currently, replays for backend errors are supported for the following SDK versions or newer:
2+
3+
- JavaScript (or related framework) [7.51.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.51.0)
4+
- Python [1.26.0](https://github.com/getsentry/sentry-python/releases/tag/1.26.0)
5+
- Node [7.48.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.48.0)
6+
- PHP [3.18.0](https://github.com/getsentry/sentry-php/releases/tag/3.18.0)
7+
- .NET [3.31.0](https://github.com/getsentry/sentry-dotnet/releases/tag/3.31.0)
8+
- Java [6.17.0](https://github.com/getsentry/sentry-java/releases/tag/6.17.0)
9+
- Ruby [5.9.0](https://github.com/getsentry/sentry-ruby/releases/tag/5.9.0)
10+
- Go [0.21.0](https://github.com/getsentry/sentry-go/releases/tag/v0.21.0)

0 commit comments

Comments
 (0)