Error¶
Guance Error Center is a full-stack error tracking and management feature designed to help teams systematically handle various errors generated during application runtime.
By intelligently aggregating error information from APM (Application Performance Monitoring), RUM (Real User Monitoring), and Logs, Guance automatically categorizes massive scattered errors into manageable Issues. Through feature extraction and noise reduction, the system removes variable information such as UUIDs and timestamps, accurately identifies the same type of errors, and significantly reduces duplicate alert interference.
In the error analysis phase, the system provides complete contextual information, including error stacks, associated performance traces, affected user sessions, and related logs and metrics. For frontend errors, it can also map back to the source code line level using SourceMap.
Furthermore, the Error Center offers a standardized processing workflow, supporting error status transitions (Triage/Assigned/Resolved/...), assignee designation, team comment collaboration, and other functions, ensuring that every error is effectively tracked and resolved in a closed loop, thereby enhancing team collaboration efficiency.
With the Error Center, the time spent switching between different functional components is significantly reduced, streamlining and optimizing the complete management process from error discovery to resolution.
Error Definition¶
Within the functional logic framework of the "Error Center," an "error" specifically refers to an abnormal event unit identified from three types of data sources—APM, RUM, and Logs—with distinct error characteristics (including error type, error message, and error stack). Through standardized processing and intelligent fingerprint calculation of error types, messages, and stack characteristics, the system automatically aggregates multiple errors with the same root cause into a unique "Error Issue."
Each Error Issue has its own lifecycle state management, following a standard workflow from "To be assigned (Triage)" to "Resolved," and is associated with complete analytical context (including performance traces, user sessions, source code mappings, and log metrics). This definition transforms traditionally scattered and repetitive alert information into trackable, analyzable, and closable technical problem entities.
Error Sources¶
The Error Center uniformly manages error information from the following three types of data:
-
Application Performance Monitoring (APM): Service exceptions and errors
-
Real User Monitoring (RUM): Client-side errors in frontend applications (Web/App)
-
Logs: Error logs recorded by systems or applications
Prerequisites for Error Generation¶
The Error Center operates in a configuration-driven manner. Before use, you need to create delivery rules to explicitly specify the data scope to be monitored (specific log indexes, APM services, or RUM applications). Once configured, the system will only perform intelligent analysis and aggregation processing on errors generated from these selected data sources.