Error Tracking¶

Guance provides an application performance monitoring error data analysis explorer, where you can quickly view the historical trends and distribution of similar errors in the trace under Application Performance Monitoring > Error Tracking, helping to quickly pinpoint performance issues.

The Error Tracking Explorer includes two lists: All Errors and Pattern Analysis:

• All Errors: Used for overall viewing of all trace errors that occur in the project application;

• Pattern Analysis: Used for quickly viewing the most frequent occurrences of trace errors that need to be resolved.

Guance Explorer provides powerful query and analysis functions. Refer to Explorer Description.

All Errors¶

In Guance workspace Application Performance Monitoring > Error Tracking, select the All Errors list to view and analyze error data from all traces.

Note: All error data statistics are based on error status status=error and contain the error_type field in the Span.

Obsy AI Error Analysis¶

Guance provides the ability to parse error data with one click. It automatically extracts key information from the data using large models 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 data entry to expand the details page;
2. Click "Obsy AI Error Analysis" in the top right corner;
3. Start anomaly analysis.

Correlation Analysis¶

In the Error Tracking Explorer, you can click any error to view the corresponding error trace details, including services, error types, error content, error distribution charts, error details, trace details, extended attributes, as well as associated logs, hosts, networks, etc.

Pattern Analysis¶

If you need to view errors with higher frequency, you can choose the Pattern Analysis list under Guance workspace Application Performance Monitoring > Error Tracking.

Pattern Analysis performs similarity calculations on all error trace data based on clustering fields. According to the selected time range in the upper right corner, it fixes the current time period and retrieves 10,000 data entries within this time period for pattern analysis. Similar error traces are aggregated, and common patterns are extracted and counted to help quickly discover abnormal traces and locate problems.

By default, aggregation is performed based on the error_message field, but you can customize up to three clustering fields.

Pattern Analysis Details¶

• In the Pattern Analysis list, you can view all related error traces by clicking any error, and then click the trace to enter the error trace details page for analysis;

• In the Pattern Analysis page, click the sort icon & to sort document quantities in ascending/descending order (default descending).

• If you need to export a specific data entry, open the detailed page of that data entry and click the icon in the top right corner.

Automatic Issue Discovery¶

Based on the data generated by Guance monitoring APM error tracking, when you enable the Automatic Issue Discovery configuration, the system will statistically summarize corresponding anomaly data according to different grouping dimensions and stack track subsequent similar issues, automatically condensing them into final Issues. Issues generated through this entry will help you intuitively obtain the context and root cause of the issue, significantly reducing the average time to solve problems.

Start Configuration¶

Note: Before enabling this configuration, you must configure rules first. Otherwise, enabling is not supported.

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

Combined Dimensions: Categorization and statistics based on configured field content combinations, including service, version, resource, error_type.

For the data source, you can add filtering conditions to filter data, and Guance will further query the data that meets the conditions, narrowing down the available data range.

Detection Frequency: Guance will query data over a 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 according to the definition here. To avoid missing information, fill in sequentially.

Among these, both the title and description of the Issue support the following template variables:

View Issues¶

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

Further Reading¶