Error Details¶

The error details page provides a complete analytical workspace for a single error. In the error list, click on a single error data entry to enter its details page.

The top of the page displays the core information of the error, including the corresponding service (APM/Log) or application name (RUM), the last trigger time, error type and description, etc.

The left side of the page displays the error handling status, including:

• Unassigned
• Assigned
• In Progress
• Resolved
• Ignored

Errors can only be claimed by users actively. Once claimed, the status automatically changes from Unassigned to Assigned, and other users cannot modify the status at this point. The right area displays the processing progress timeline, clearly showing the status transition records.

Error Distribution Chart¶

The error distribution chart is based on the occurrence time of the most recent error and the time range selected on the page, showing the trend of this issue during this period.

Above the distribution chart, key information such as impact statistics, first occurrence time, duration, and cumulative trigger count is also provided.

Error Description¶

The system will display the relevant description of this error, including the following information:

1. Detection dimensions: including service (service), environment (env), version (version);

2. Error details: displays the core content of the last error;

3. APM/Log: If this error data includes a trace identifier (trace_id), the system will further display the complete trace details:

   • Flame graph: visually displays method call stacks and time consumption distribution

   • Span list: lists all call units in this trace and their detailed information

   • Waterfall chart: displays the sequence and duration of each call in chronological order

   • Details panel: click on any call unit to view its detailed attributes, logs, and context information

4. RUM: Displays the detailed content of the most recent error, including error message (error_message) and error stack (error_stack). If the error is associated with SourceMap, the system will automatically parse and map it to the source code location, supporting expansion and zoom to view the complete stack information.

   • Session details: displays the user session details that triggered this error, including basic session information and a session replay thumbnail. Click the thumbnail to play the complete operation recording in a side-slide overlay on the current page, recreating the real user scenario when the error occurred

   • Session event list: displays all interaction events in this user session, showing the user's operation sequence in chronological order to help understand the complete operation path before the error occurred

Operation Records¶

In the error details page, you can fully track the entire handling process of the error issue through "Operation Records", which includes three key actions: error trigger generation, status changes (e.g., from "Unassigned" to "In Progress"), and responsible person changes. All records are arranged in reverse chronological order of occurrence, making it easy for you to quickly understand the latest dynamics and complete handling context of the error.

Collaboration Records¶

You can use the comment function at the bottom of the page for team collaboration on the current details page, supporting adding text, links, or uploading attachments.

All collaboration content will be summarized in the collaboration records section. The system automatically records the complete operation log, including error triggering, status changes, operation records, responsible person adjustments, and upgrade notifications, forming a clear audit trail for subsequent tracking and review.

Associated Views¶

The error details page provides targeted correlation analysis based on the error source (APM/RUM/Log). All analysis data is based on the most recent error occurrence time, defaulting to show the associated context from the last 2 hours, specifically including comprehensive views such as associated traces, analysis dashboards, infrastructure dependencies, service topology, and associated logs.

Further Reading¶