For detailed grouping rules, please refer to Error Grouping.
Issue Information Overview
| Item | Description |
|---|---|
| Error type and error message | Core identifying information of the Issue |
| File path where error occurred | Locate error source |
| Service name | Associated service |
| Error cause | System-inferred possible root cause |
| Whether issue has regressed | Indicates if a resolved issue has reappeared |
| First and last occurrence time | Issue lifecycle information |
| Occurrence count chart | Trend over time |
| Occurrence count in selected time period | Statistical data |
Issue Status
Issues have 4 statuses, with transitions as follows:
| Status | Description |
|---|---|
| For Review | Newly discovered issues that need attention |
| Reviewed | Confirmed issues being fixed |
| Resolved | Issues that have been fixed |
| Ignored | Issues that don’t need handling |
Filtering and Sorting
- Time Range
- Sort Options
- Filters
The timeline in the upper right corner of the browser allows you to display Issues that had errors during the selected time period. You can:
- Select a preset range from the dropdown menu
- Directly modify the time
- Enter natural language for filtering
Error Cause Classification
Flashcat adds an error cause classification to each Issue when created, helping improve fault localization efficiency.| Error Cause | Description |
|---|---|
| Code Error | Errors caused by code defects |
| Illegal Object Access | Code accessed a null or undefined object |
| Invalid Parameter | Function called with invalid parameters |
| Network Error | Server response too slow or poor network speed |
| API Request Failed | API endpoint returned an error status code |
| Unknown Error | Unable to locate this error type |
Regression
Regression refers to previously fixed bugs reappearing.
Issue Details
Click any Issue to open the details panel and view more information.
Basic Information
Basic Information
The top of the panel displays basic Issue information, such as status and error cause. You can also understand the Issue lifecycle: first and last occurrence dates, duration, and error occurrence count over time (aggregated by time granularity).
Label Distribution
Label Distribution
In the label distribution section, you can view the proportion of different labels under this Issue across various dimensions, quickly determining the impact scope and helping locate root causes.Currently supports labels like
view_name, browser_name, version, env, etc.Error Sample
Error Sample
By default, displays the most recent error information reported during the Issue’s occurrence as an error sample. You can also switch through the navigation bar.
Error Stack
Error Stack
View error context and stack information. If source code has been uploaded, you can see the stack information when the error occurred.
You can view uploaded source code information in “Application Management” - “Source Code Management”. See Source Mapping for details.
Session Timeline
Session Timeline
View the total number of Session events for the current error sample, as well as user resource access and operations before and after the error occurred.
Currently displays up to 20 context items including the current Error event. You can view more log information in the Session Viewer module later.
Attributes
Attributes
Error events carry a series of attributes when reported. You can view current Session, view, user, and other information in the attributes section to help troubleshoot issues.
Issue Alerts
Discover problems immediately when they occur, giving you the opportunity to proactively identify and fix them before they become severe.
For detailed alert configuration instructions, please refer to Issue Alerts.
Best Practices
Configure Source Mapping
Facilitates problem localization in production environments
Add User Information
Configure user-related information to provide better error context
Set Alert Policies
Configure appropriate channels and escalation rules for errors
Regular Error Analysis
Regularly check error reports to discover potential issues
Team Collaboration
Use team ownership features to ensure issues are quickly assigned to relevant teams
Monitor Regressions
Closely monitor potential regressions of resolved issues