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: content/en/real_user_monitoring/error_tracking/browser.md
+21-20Lines changed: 21 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,29 +17,29 @@ further_reading:
17
17
18
18
## Overview
19
19
20
-
Error Tracking processes errors collected from the browser by the RUM Browser SDK. Whenever a [source][1] or [custom][2] error containing a stack trace is collected, Error Tracking processes and groups it under an issue, or group of similar errors.
20
+
Error Tracking processes errors collected from the browser by the RUM Browser SDK. Whenever a [source][1], [custom][2], or [report][3] error containing a stack trace is collected, Error Tracking processes and groups it under an issue, or group of similar errors.
21
21
22
-
Your crash reports appear in [**Error Tracking**][3].
22
+
Your crash reports appear in [**Error Tracking**][4].
23
23
24
24
## Setup
25
25
26
-
If you have not set up the Browser SDK yet, follow the [in-app setup instructions][4] or see the [Browser RUM setup documentation][5].
26
+
If you have not set up the Browser SDK yet, follow the [in-app setup instructions][5] or see the [Browser RUM setup documentation][6].
27
27
28
-
1. Download the latest version of the [RUM Browser SDK][6].
29
-
2. Configure your application's `version`, `env`, and `service` when [initializing the SDK][7].
30
-
3.[Upload your JavaScript source maps][8] to access unminified stack traces.
28
+
1. Download the latest version of the [RUM Browser SDK][7].
29
+
2. Configure your application's `version`, `env`, and `service` when [initializing the SDK][8].
30
+
3.[Upload your JavaScript source maps][9] to access unminified stack traces.
31
31
32
32
## Link errors with your source code
33
33
34
-
In addition to sending source maps, the [Datadog CLI][9] reports Git information such as the commit hash, repository URL, and a list of tracked file paths in the code repository.
34
+
In addition to sending source maps, the [Datadog CLI][10] reports Git information such as the commit hash, repository URL, and a list of tracked file paths in the code repository.
35
35
36
-
Error Tracking and RUM can use this information to correlate errors with your source code, allowing you to pivot from any stack trace frame to the related line of code in [GitHub][10], [GitLab][11] and [Bitbucket][12].
36
+
Error Tracking and RUM can use this information to correlate errors with your source code, allowing you to pivot from any stack trace frame to the related line of code in [GitHub][11], [GitLab][12] and [Bitbucket][13].
37
37
38
38
{{< img src="real_user_monitoring/error_tracking/link_to_git_js_example.mp4" alt="Link from a stack frame to the source code" video=true >}}
39
39
40
40
<divclass="alert alert-info">Linking from stack frames to source code is supported in the <ahref="https://github.com/DataDog/datadog-ci/tree/master/src/commands/sourcemaps#sourcemaps-command">Datadog CLI</a> version <code>0.12.0</code> version and later.</div>
41
41
42
-
For more information, see the [Datadog Source Code Integration][13].
42
+
For more information, see the [Datadog Source Code Integration][14].
43
43
44
44
### Limitations
45
45
@@ -56,14 +56,15 @@ Source maps are limited to **500** MB each.
0 commit comments