Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit eeca08c

Browse files
author
ada
committed
Updated based on reviewer feedback
1 parent cc62b8e commit eeca08c

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

rum/error-aggregates.rst

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -105,9 +105,7 @@ The information in most raw crash stack traces is not fully human-readable. To m
105105
JavaScript error aggregation
106106
==========================================================================================
107107

108-
Splunk RUM's :guilabel:`APPLICATION SUMMARY DASHBOARD` groups errors by error ID. Each group's error ID is unique. For more information about the error ID, see :ref:`about-error-id`.
109-
110-
The JavaScript Errors metric in RUM displays JavaScript errors (grouped by error ID) which occur most often in your applications. The error ID is created by hashing the associated stack trace, error message, and error type. When you drill into an error, you can see the error type, the error message, associated stack trace, and the trend of the error frequency. For more information about the error ID, see :ref:`about-error-id`.
108+
Splunk RUM's :guilabel:`APPLICATION SUMMARY DASHBOARD` displays JavaScript errors (grouped by error ID) which occur most often in your applications. The error ID is created by hashing the associated stack trace, error message, and error type. When you drill into an error, you can see the error type, the error message, associated stack trace, and the trend of the error frequency. For more information about the error ID, see :ref:`about-error-id`.
111109

112110
To see errors from a specific browser application:
113111

0 commit comments

Comments
 (0)