Error Tracking

Master RUM error tracking features to quickly discover and resolve website issues.

RUM (Real User Monitoring) is a powerful user experience monitoring tool focused on helping developers quickly discover and resolve issues in websites and applications, ensuring system stability and smooth user experience. It automatically captures various types of errors and provides detailed contextual data, enabling you to precisely locate the root cause of problems and take timely action to fix them.

Core Features

Error Tracking

Automatically captures JavaScript errors, network request failures, resource loading errors, and other issues, providing detailed error stack traces and contextual data

Error Reporting

Supports both automatic error capture and manual error reporting, allowing you to record handled errors in business logic with additional context information

Error Grouping

Groups similar error events into the same Issue, reducing duplicate alerts and helping development teams identify and handle problems more efficiently

Source Mapping

By uploading SourceMap files, maps minified code to original source code, directly locating the specific position in the original code

Value and Benefits

Benefit	Description
Improve Problem Resolution Efficiency	Quickly locate the root cause of problems, reduce troubleshooting time, and improve the efficiency of development and operations teams
Optimize User Experience	Timely discover and resolve issues affecting user experience, improving user satisfaction and loyalty
Reduce Business Risk	Avoid business losses caused by system failures, ensuring stable business operations
Provide Data Support	Detailed error data and contextual information provide strong support for business decisions, helping you continuously optimize products

Use Cases

Frontend Development Debugging

During development, quickly locate and resolve errors in JavaScript code, improving development efficiency.

Production Environment Monitoring

Real-time monitoring of errors in production environments, timely discovery and handling of potential issues, ensuring system stability.

User Experience Analysis

Understand issues users encounter during use, make targeted product improvements, and enhance user experience.

Error Tracking Workflow

RUM error tracking consists of two key phases: Problem Discovery and Problem Localization.

1. Problem Discovery

   Quickly discovering error trigger points is the first step in diagnosis. RUM provides the following ways to help you identify problems:

   • Data Analysis: View error rates, error types, and other data trends through the “Errors” tab in the Analytics Dashboard
   • Alert Notifications: By enabling alerts in the application and linking with channels, you can be notified immediately when errors occur
   • Active Inspection: Observe error trends in the Error Tracking module, such as JavaScript errors, network errors, etc.
2. Problem Localization

   RUM provides rich error data and contextual information to help you precisely locate the root cause.

Core Error Data

Error Type	Description
JavaScript Errors	Runtime errors, syntax errors, etc.
Network Request Errors	API call failures, timeouts, etc.
Resource Loading Errors	Image, script, and other resource loading failures
Framework-related Errors	Component errors in React, Vue, and other frameworks

Contextual Information

• User Environment: Browser type, device model, operating system
• Error Stack: Detailed call stack information
• Session Timeline: Operation path that triggered the error

Problem Classification and Localization

Problem Type	Typical Symptoms	Possible Causes	Key Metrics
JavaScript Errors	Feature failure, console errors	Code logic errors, browser compatibility issues	Error rate, error type
Network Request Errors	Request timeout, connection interruption	Slow API response, poor network quality	Request latency, connection success rate
Resource Loading Errors	Image/script loading failure	CDN configuration errors, incorrect resource paths	Resource loading failure rate
Framework-related Errors	Component rendering failure	Component logic errors, state management issues	Component error rate

Problem Localization Tools

Error Analysis Panel

Through the error analysis panel, you can view the aggregated Issue list, error trends, and detailed information.

Source Mapping

After uploading SourceMaps, you can view the original source code location directly in the stack trace.

After resolving a problem, you can transition the Issue status in the system and continue to monitor error data trends.

Next Steps

Error Reporting

Learn about error reporting rules and methods

View Errors

View and analyze error details

Source Mapping

Configure source mapping to improve debugging efficiency

Error Grouping

Learn about error grouping mechanisms