Error¶

You can view frontend errors sent by the browser during user application usage, including error types and error details.

In the Error Explorer, you can:

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

• Restore obfuscated code through Sourcemap conversion, facilitating error troubleshooting and source code localization, helping users solve problems faster.

Explorer List¶

All Errors¶

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

• Error content Load failed: Errors without response, default SDK adds Load failed.

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

Pattern Analysis¶

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

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

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

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

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

Details Page¶

Click on the data in the list to view the error details, including error details, extended fields, and associated traces.

Source¶

In 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 errors with high similarity and displays the error distribution trend based on the selected time range in the Explorer, helping you intuitively view the time points or ranges where errors frequently occur, 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 code leakage and other security issues, files are usually transformed and compressed during the packaging process. While these measures ensure code security, they also result in the collected error stack information being obfuscated, making it difficult to directly locate issues, complicating subsequent bug troubleshooting.

Guance provides the Sourcemap function for applications, supporting the restoration of obfuscated code, facilitating error troubleshooting and source code localization, helping users solve problems 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¶

In RUM, configure Sourcemap conversion, parsed code example:

Original Code Example¶

Using Datakit Collector to configure Sourcemap conversion, parsed code example:

Note: If users configure Sourcemap in both RUM and Datakit Collector, the parsed format configured in RUM will be displayed.

Extended Fields¶

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

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

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

Obsy AI Error Analysis¶

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

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

Issue Auto Discovery¶

Based on Guance monitoring RUM Error data, when you enable the Issue Auto Discovery configuration, the system will statistically analyze the corresponding abnormal data based on different grouping dimensions, and perform stack tracking for subsequent similar problems, automatically condensing them, and finally generating Issues. Issues generated through this entry will help you obtain the context and root cause of the problem, significantly reducing the average time to solve problems.

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

Combination Dimensions: Statistical classification based on the combination of configuration field contents, including app_name, env, version, error_type.

Based on combination dimensions, you can add filter conditions, and Guance will further query and classify the 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 based on the definition here. To avoid information loss, please fill in sequence.

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

View Issue¶

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

Further Reading¶