Error (Errors)¶

You can view frontend errors issued by the browser during application usage, including error types and error content.

In the Error Explorer, you can:

• View all error types and their related error details in one place;
• Through Sourcemap conversion, deobfuscate the code to facilitate source code positioning during error troubleshooting, helping users solve problems faster.

Explorer List¶

All Errors¶

In the Error Explorer, you can quickly view page addresses, code error types, and error content during user access.

• Error content Load failed: i.e., errors without a response, which the default SDK adds as Load failed;
• Error content Network request failed: i.e., response returns an error.

Pattern Analysis¶

If you need to view errors with higher occurrence frequencies, you can select Pattern Analysis under Guance workspace Synthetic Tests > Explorer > Error.

Pattern Analysis performs similarity calculations on all error chain data based on clustering fields. It fixes the current time period according to the selected time range in the upper right corner and retrieves 10,000 data points for cluster analysis within that time period. Similar high-error chains are aggregated, extracting and statistically analyzing common Patterns, aiding in the rapid discovery of abnormal chains and problem localization.

By default, it aggregates based on the error_message field, but up to 3 clustering fields can be defined.

• In the Pattern Analysis list, you can click any error to view all associated Errors and click the chain to enter the detail page for analysis;

• On the Pattern Analysis page, clicking the sort icon & , you can sort document counts in ascending/descending order (default is descending).

Detail Page¶

By clicking on the data detail page in the list, you can view detailed information about errors during user access, including error details, extended fields, and associated chains.

Source¶

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

Error Distribution Chart¶

The Error Distribution Chart aggregates similar errors and automatically selects appropriate time intervals based on the selected time range in the explorer to display the distribution trend of errors, helping you visually identify frequent error times or time ranges, quickly locating error issues.

Error Details¶

In the Error Details, you can view the specific content of the error.

Sourcemap Conversion¶

When applications are released in production environments, to prevent issues like code leaks and other security concerns, files are usually transformed and compressed during the packaging process. While these measures ensure code safety, they also result in collected error stack information being obfuscated, making it difficult to directly locate problems and complicating subsequent Bug troubleshooting.

Guance provides Sourcemap functionality for applications, supporting the deobfuscation of code to facilitate source code positioning during error troubleshooting, helping users solve problems faster.

You can configure this through RUM Sourcemap Configuration or Datakit Collector Sourcemap Conversion. Once configured, 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¶

Example of parsing code configured for Sourcemap in RUM:

Original Code Example¶

Example of parsing code configured for Sourcemap using Datakit collector:

Note: If users configure Sourcemap in both RUM and the Datakit collector simultaneously, the parsed format from RUM configuration will be displayed.

Extended Fields¶

In the search bar, you can input field names or values to quickly search and locate;

After selecting field aliases, you can view them after the field names. You can choose as needed.

In the chain detail page, you can view relevant field attributes of the current chain in Extended Fields:

Obsy AI Error Analysis¶

Guance provides the ability to automatically parse error data with a single click. It uses large models to automatically extract key information from the data and combines online search engines and operations knowledge bases to quickly analyze possible causes of failure and provide preliminary solutions.

1. Click on a single piece of data to expand the detail page;
2. Click "Obsy AI Error Analysis" in the upper right corner;
3. Start anomaly analysis.

Issue Auto Discovery¶

Based on Guance monitoring RUM Error data, when you enable the Issue Auto Discovery configuration, the system will statistically aggregate corresponding anomaly data based on different grouping dimensions and perform stack trace tracking on subsequent similar issues, automatically condensing them into Issues. 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: i.e., the activation entry on the current configuration page.

Composite Dimensions: Based on the combination of configuration field contents for classification and statistics, including app_name, env, version, error_type.

Based on composite dimensions, filtering conditions can be added, Guance will query and classify data that meets the conditions further.

Detection Frequency: Guance will query data time ranges 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 definitions here. To avoid missing information, they must be filled out sequentially.

In both the Title and Description sections of an Issue, the following template variables are supported:

View Issues¶

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

Further Reading¶