Error¶

You can view frontend errors sent by the browser when users use the application, including error types, error content, etc.

In the Error explorer, you can:

• Centrally view all error types and their related error details.

• Restore obfuscated code through Sourcemap conversion, facilitating source code location during error troubleshooting and helping users resolve issues faster.

Explorer List¶

All Errors¶

In the Error explorer, you can quickly view the page addresses, code error types, error content, etc., during user visits.

• Error content "Load failed": errors without a response, default SDK adds "Load failed".

• Error content "Network request failed": errors where response returns an error.

Pattern¶

If you need to view errors with high frequency, you can go to the Guance workspace User Analysis > Explorer > Error and select the Pattern list.

Pattern analysis performs similarity calculation and analysis on all error trace data based on clustering fields. It fixes the current time period based on the selected time range in the upper right corner, retrieves 10,000 data points within that period for clustering analysis, aggregates error traces with high similarity, extracts and counts common Pattern clusters, helping to quickly detect abnormal traces and locate problems.

By default, aggregation is performed based on the error_message field. You can customize the input clustering fields, with a maximum of 3.

• In the Pattern list, you can click on any error to view all associated Errors. Clicking on a trace will take you to the details page for analysis.

• On the Pattern page, click the sort icons & to sort the document count in ascending/descending order (default is descending).

Details Page¶

Click on the data you want to view in the list to access the details page of the user's error, including error details, extended fields, associated traces, etc.

Source¶

Under Source, you can view the Session / View / Action details of the current Error, filter/copy the current Session ID / View ID / Action ID.

Error Distribution Chart¶

The error distribution chart aggregates and counts errors with high similarity. It automatically selects the corresponding time interval based on the time range chosen in the explorer to display the error distribution trend, helping you intuitively view the time points or ranges where errors occur frequently, and quickly locate error issues.

Error Details¶

In the error details, you can view the specific content of the error.

Sourcemap Conversion¶

When applications are released in a production environment, files are typically transformed, compressed, etc., during the packaging process to prevent code leakage and other security issues. While these measures protect code security, they also result in collected error stack information being obfuscated, making it impossible to directly locate problems and complicating subsequent Bug troubleshooting.

Guance provides the Sourcemap function for applications, supporting the restoration of obfuscated code, facilitating source code location during error troubleshooting, and helping users resolve issues faster.

You can configure Sourcemap through RUM Sourcemap Configuration or Datakit Collector Sourcemap Conversion. After configuration, you can view the parsed code and original code in the error details.

Note: Currently, only Web-type applications support Sourcemap configuration in RUM.

Parsed Code Example¶

Sourcemap conversion configured in RUM, parsed code example:

Original Code Example¶

Sourcemap conversion configured using the Datakit collector, parsed code example:

Note: If the user has configured Sourcemap in both RUM and the Datakit collector, the parsed format from the RUM configuration is displayed.

Extended Fields¶

In the search bar, you can enter the field name or value to quickly search and locate.

After checking the field alias, you can view it after the field name; you can choose as needed.

In the trace details page, you can view the relevant field attributes of the current trace under Extended Fields:

Obsy AI Error Analysis¶

Guance provides the capability to parse error data with one click. It uses large models to automatically extract key information from the data, combines online search engines and operation and maintenance knowledge bases, quickly analyzes possible fault causes, and provides preliminary solutions.

1. Click on a single data point to expand the details page.
2. Click "Obsy AI Error Analysis" in the upper right corner.
3. Begin anomaly analysis.

Issue Auto-Discovery¶

Based on the data generated by Guance monitoring RUM Errors, when you enable the Issue Auto-Discovery configuration, the system will statistically analyze corresponding abnormal data based on different grouping dimensions, track the stack for subsequent similar problems, automatically condense them, and finally generate an Issue. Issues generated through this entry will help you obtain the context and root cause of the problem, significantly reducing the average time to resolve issues.

Data Source: The enablement entry of the current configuration page.

Combination Dimensions: Categorize and count based on the combination of configured field contents, including app_name, env, version, error_type.

Based on the combination dimensions, you can add filter conditions. Guance will further query and categorize data that meets the conditions.

Detection Frequency: Guance will query the data time range based on the frequency you select, including 5 minutes, 10 minutes, 15 minutes, 30 minutes, and 1 hour.

Issue Definition: After enabling this configuration, Issues will be presented externally based on the definition here. To avoid missing information, fill in sequentially.

Both the Title and Description of the Issue support the use of the following template variables:

Viewing Issues¶

After saving the configuration and enabling it, Issues automatically discovered and generated by the system will be displayed in Console > Incident.

Further Reading¶