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: develop-docs/sdk/telemetry/traces/index.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -232,12 +232,12 @@ If no `tracesSampler` callback is used, the SDK fully inherits sampling decision
232
232
233
233
The random value is set according to the following rules:
234
234
235
-
1. When an SDK starts a new trace, `sample_rand` is always set to a random number in the range of `[0, 1]`. This explicitly includes traces that aren't sampled, as well as when the `tracesSampleRate` is set to `0.0` or `1.0`.
235
+
1. When an SDK starts a new trace, `sample_rand` is always set to a random number in the range of `[0, 1)` (including 0.0, excluding 1.0). This explicitly includes traces that aren't sampled, as well as when the `tracesSampleRate` is set to `0.0` or `1.0`.
236
236
2. It is _recommended_ to generate the random number deterministically using the trace ID as seed or source of randomness. The exact method by which the random number is created is implementation defined and may vary between SDK implementations. See 4. on why this behaviour is desirable.
237
237
3. On incoming traces, an SDK assumes the `sample_rand` value along with the rest of the DSC, overriding an existing value if needed.
238
238
4. If `sample_rand` is missing on an incoming trace, the SDK creates and from now on propagates a new random number on-the-fly, based on the following rules:
239
239
1. If `sample_rate` and `sampled` are propgated, create `sample_rand` so that it adheres to the invariant. This means, for a decision of `True` generate a random number in half-open range `[0, rate)` and for a decision of `False` generate a random number in range `[rate, 1]`.
240
-
2. If the sampling decision is missing, generate a random number in range of `[0, 1]`, like for a new trace.
240
+
2. If the sampling decision is missing, generate a random number in range of `[0, 1)` (including 0.0, excluding 1.0), like for a new trace.
241
241
242
242
The SDK should always use the stored random number (`sentry-sample_rand`) for sampling decisions and should no longer rely on `math.random()` or similar functions in tracing code:
Copy file name to clipboardExpand all lines: docs/platforms/android/enriching-events/attachments/index.mdx
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,20 @@ The filename is the name of the file to display in Sentry. When using bytes you
27
27
28
28
The type of content stored in this attachment. Any [MIME type](https://www.iana.org/assignments/media-types/media-types.xhtml) may be used; the default is `application/octet-stream`.
29
29
30
+
`mimetype`
31
+
32
+
The specific media content type that determines how the attachment is rendered in the Sentry UI. We currently support and can render the following MIME types:
33
+
34
+
-`text/plain`
35
+
-`text/css`
36
+
-`text/csv`
37
+
-`text/html`
38
+
-`text/javascript`
39
+
-`text/json` or `text/x-json` or `application/json` or `application/ld+json`
Copy file name to clipboardExpand all lines: docs/platforms/android/index.mdx
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,8 +49,6 @@ Select which Sentry features you'd like to install in addition to Error Monitori
49
49
50
50
Sentry captures data by using an SDK within your application's runtime. These are platform-specific and allow Sentry to have a deep understanding of how your application works.
51
51
52
-
In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](https://docs.sentry.io/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](https://docs.sentry.io/product/explore/profiling/). To enable tracing and/or profiling, click the corresponding checkmarks to get the code snippets.
53
-
54
52
We recommend installing the SDK through our [Sentry Wizard](https://github.com/getsentry/sentry-wizard) by running the following command inside your project directory:
Copy file name to clipboardExpand all lines: docs/platforms/android/session-replay/index.mdx
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,9 @@ description: "Learn how to enable the Beta of Mobile Session Replay in your app.
7
7
8
8
<Note>
9
9
10
-
Mobile support for Session Replay is in Beta. Features available in Beta are still work-in-progress and may have bugs. We recognize the irony.
10
+
Mobile support for Session Replay is in beta until January 6th, 2025. Features available in beta are still work-in-progress and may have bugs. We recognize the irony.
11
+
12
+
All beta users will continue to receive 2 months free of Session Replay for Mobile once we transition to GA.
11
13
12
14
If you have any questions, feedback or would like to report a bug, please open a [GitHub issue](https://github.com/getsentry/sentry-java/issues/new?assignees=&labels=Platform%3A+Android%2CType%3A+Bug&projects=&template=bug_report_android.yml) with a link to a relevant replay in Sentry if possible.
Copy file name to clipboardExpand all lines: docs/platforms/apple/common/enriching-events/attachments/index.mdx
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,20 @@ The filename is the name of the file to display in Sentry. When using bytes you
27
27
28
28
The type of content stored in this attachment. Any [MIME type](https://www.iana.org/assignments/media-types/media-types.xhtml) may be used; the default is `application/octet-stream`.
29
29
30
+
`mimetype`
31
+
32
+
The specific media content type that determines how the attachment is rendered in the Sentry UI. We currently support and can render the following MIME types:
33
+
34
+
-`text/plain`
35
+
-`text/css`
36
+
-`text/csv`
37
+
-`text/html`
38
+
-`text/javascript`
39
+
-`text/json` or `text/x-json` or `application/json` or `application/ld+json`
40
+
-`image/jpeg`
41
+
-`image/png`
42
+
-`image/gif`
43
+
30
44
## Uploading Attachments
31
45
32
46
Attachments live on the <PlatformLinkto="/enriching-events/scopes/">Scope</PlatformLink>. You can either add an attachment on the global scope to be sent with every event or add it on the <PlatformLinkto="/enriching-events/scopes/#local-scopes">local Scope</PlatformLink> to just send the attachment with one specific event.
In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/).
In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/).
30
+
31
+
</PlatformSection>
32
+
23
33
Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below.
Sentry captures data by using an SDK within your application's runtime. These are platform-specific and allow Sentry to have a deep understanding of how your application works.
In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](https://docs.sentry.io/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](https://docs.sentry.io/product/profiling/). To enable tracing and/or profiling, click the corresponding checkmarks to get the code snippets.
49
+
50
+
Sentry captures data by using an SDK within your application's runtime. These are platform-specific and allow Sentry to have a deep understanding of how your application works.
38
51
39
52
<PlatformSectionnotSupported={["apple.ios"]}>
40
53
@@ -72,8 +85,9 @@ If you prefer, you can also [set up the SDK manually](/platforms/apple/guides/io
72
85
73
86
To capture all errors, initialize the SDK as soon as possible, such as in your `AppDelegate``application:didFinishLaunchingWithOptions` method:
Copy file name to clipboardExpand all lines: docs/platforms/apple/guides/ios/session-replay/index.mdx
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,11 @@ description: "Learn how to enable the Beta of Mobile Session Replay in your app.
7
7
8
8
<Note>
9
9
10
-
Mobile support for Session Replay is in Beta. Features available in Beta are still work-in-progress and may have bugs. We recognize the irony.
10
+
Mobile support for Session Replay is in beta until January 6th, 2025. Features available in beta are still work-in-progress and may have bugs. We recognize the irony.
11
11
12
-
If you have any questions, feedback or would like to report a bug, please open a [GitHub issue](https://github.com/getsentry/sentry-cocoa/issues/new?assignees=&labels=Platform%3A+Cocoa%2CType%3A+Bug&projects=&template=bug.yml) with a link to a relevant replay in Sentry if possible.
12
+
All beta users will continue to receive 2 months free of Session Replay for Mobile once we transition to GA.
13
+
14
+
If you have any questions, feedback or would like to report a bug, please open a [GitHub issue](https://github.com/getsentry/sentry-java/issues/new?assignees=&labels=Platform%3A+Android%2CType%3A+Bug&projects=&template=bug_report_android.yml) with a link to a relevant replay in Sentry if possible.
13
15
14
16
</Note>
15
17
@@ -110,4 +112,4 @@ A: Text views, input views, images, video players and webviews are all masked by
110
112
111
113
Q: What's the lowest version of iOS supported?
112
114
113
-
A: Session Replay recording happens even on the lowest version supported by the Sentry SDK, which is aligend with appstore support.
115
+
A: Session Replay recording happens even on the lowest version supported by the Sentry SDK, which is aligend with appstore support.
Copy file name to clipboardExpand all lines: docs/platforms/dart/enriching-events/attachments/index.mdx
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,20 @@ The filename is the name of the file to display in Sentry. When using bytes you
27
27
28
28
The type of content stored in this attachment. Any [MIME type](https://www.iana.org/assignments/media-types/media-types.xhtml) may be used; the default is `application/octet-stream`.
29
29
30
+
`mimetype`
31
+
32
+
The specific media content type that determines how the attachment is rendered in the Sentry UI. We currently support and can render the following MIME types:
33
+
34
+
-`text/plain`
35
+
-`text/css`
36
+
-`text/csv`
37
+
-`text/html`
38
+
-`text/javascript`
39
+
-`text/json` or `text/x-json` or `application/json` or `application/ld+json`
40
+
-`image/jpeg`
41
+
-`image/png`
42
+
-`image/gif`
43
+
30
44
## Uploading Attachments
31
45
32
46
Attachments live on the <PlatformLinkto="/enriching-events/scopes/">Scope</PlatformLink>. You can either add an attachment on the global scope to be sent with every event or add it on the <PlatformLinkto="/enriching-events/scopes/#local-scopes">local Scope</PlatformLink> to just send the attachment with one specific event.
Copy file name to clipboardExpand all lines: docs/platforms/dotnet/common/enriching-events/attachments/index.mdx
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,20 @@ The filename is the name of the file to display in Sentry. When using bytes you
33
33
34
34
The type of content stored in this attachment. Any [MIME type](https://www.iana.org/assignments/media-types/media-types.xhtml) may be used; the default is `application/octet-stream`.
35
35
36
+
`mimetype`
37
+
38
+
The specific media content type that determines how the attachment is rendered in the Sentry UI. We currently support and can render the following MIME types:
39
+
40
+
-`text/plain`
41
+
-`text/css`
42
+
-`text/csv`
43
+
-`text/html`
44
+
-`text/javascript`
45
+
-`text/json` or `text/x-json` or `application/json` or `application/ld+json`
46
+
-`image/jpeg`
47
+
-`image/png`
48
+
-`image/gif`
49
+
36
50
## Uploading Attachments
37
51
38
52
Attachments live on the <PlatformLinkto="/enriching-events/scopes/">Scope</PlatformLink>. You can either add an attachment on the global scope to be sent with every event or add it on the <PlatformLinkto="/enriching-events/scopes/#local-scopes">local Scope</PlatformLink> to just send the attachment with one specific event.
0 commit comments