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/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:
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/javascript/guides/react/features/react-router/v6.mdx
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,10 @@ Update your `Sentry.browserTracingIntegration` to `Sentry.reactRouterV6BrowserTr
16
16
17
17
<Alertlevel="warning">
18
18
19
-
Make sure you call `Sentry.init`, **before** you wrap your `<Routes />` component or the `useRoutes` hook. Otherwise, the routing instrumentation may not work properly.
19
+
To ensure proper routing instrumentation, initialize Sentry by calling `Sentry.init`**before**:
Copy file name to clipboardExpand all lines: docs/platforms/javascript/guides/react/features/react-router/v7.mdx
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,10 @@ Update your `Sentry.browserTracingIntegration` to `Sentry.reactRouterV7BrowserTr
17
17
18
18
<Alertlevel="warning">
19
19
20
-
Make sure you call `Sentry.init`, **before** you wrap your `<Routes />` component or the `useRoutes` hook. Otherwise, the routing instrumentation may not work properly.
20
+
To ensure proper routing instrumentation, initialize Sentry by calling `Sentry.init`**before**:
Copy file name to clipboardExpand all lines: docs/platforms/unreal/configuration/environments.mdx
+13-6Lines changed: 13 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,14 +4,14 @@ description: "Learn how to configure your SDK to tell Sentry about your environm
4
4
sidebar_order: 30
5
5
---
6
6
7
-
Environments tell you where an error occurred, whether that's in your production system, your staging server, or elsewhere.
8
-
It help you better filter issues, releases, and user feedback in the Issue Details page of sentry.io, which you learn more about in our [documentation that covers using environments](/product/sentry-basics/environments/).
7
+
Environments in Sentry let you know where an error occurred, (such as in production, staging server, or another location).
8
+
They make it easier to filter issues, releases, and user feedback on the Issue Details page, (which you can navigate to by clicking any issue on the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues/) page). To learn more, read our docs about [using environments](/product/sentry-basics/environments/).
9
9
10
10
Sentry automatically creates an environment when it receives an event with the `environment` parameter set.
11
11
12
-
By default, the SDK reports `Editor` when running inside the Unreal Engine Editor.
13
-
For shipping builds it'll use `Release` and in other configurations it'll use `FApp::GetBuildConfiguration()`
14
-
You can also set the default environment to `Release`, `Development`, or `Debug` in your build configuration or override the environment value programatically.
12
+
When running inside the Unreal Engine Editor, the SDK reports the environment as `Editor`. For shipping builds, it defaults to `Release`.
13
+
In other configurations it uses the `FApp::GetBuildConfiguration()`.
14
+
You can also set the default environment to `Release`, `Development`, or `Debug` in your build configuration, or override it programmatically.
Environments are case-sensitive. The environment name can't contain newlines, spaces or forward slashes, can't be the string "None", or exceed 64 characters. You can't delete environments, but you can [hide](/product/sentry-basics/environments/#hidden-environments) them.
32
+
**Important things to note about environments:**
33
+
34
+
- Environment names are case-sensitive.
35
+
- Names cannot include new lines, spaces, or forward slashes.
36
+
- Certain strings, like "None", aren't allowed.
37
+
- The maximum length for an environment name is 64 characters.
38
+
- Environments can't be deleted, but can be [hidden](/product/sentry-basics/environments/#hidden-environments) if no longer needed.
Copy file name to clipboardExpand all lines: platform-includes/capture-error/go.mdx
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,11 @@
1
-
To capture an event in Go, you can pass any struct implementing an `error` interface to `CaptureException()`. If you use a 3rd party library instead of native `errors` package, we'll do our best to extract a stack trace.
1
+
To capture an event in Go, you can pass any struct implementing an `error` interface to `CaptureException()`. If you use a 3rd party library instead of the native `errors` package and it implements the `Unwrap() error` or `Cause() error` method, we'll follow the chain of errors and extract the stack trace from the root cause.
2
2
3
3
The SDK is fully compatible with (but not limited to):
4
4
5
5
-`github.com/pkg/errors`
6
6
-`github.com/go-errors/errors`
7
7
-`github.com/pingcap/errors`
8
+
-`github.com/rotisserie/eris`
8
9
9
10
If there is an errors package that's not working out of the box, let us know!
0 commit comments