Error tracing

Home > Select Project > Analysis > Error Tracking

Browser Monitoring collects the browser front-end errors. It includes the error messages and error stack information, browser, OS, device, and page URL.

Exploring a error

You can see browser errors that have occurred over time.

1. In , set a desired time. It can be set up to 1 day in advance.

2. Select one of the bar graphs displayed on the chart.

   From the time list, you can select the time detail when an error occurred among the data collected every 10 minutes.

3. Below the chart, you can see a list of browser errors that occurred at the selected time.

   If you type specific keywords in the input field, the matching text is highlighted in the list.

4. To check the details of the error, select on the utmost left.

Checking the error information details

The browser error has the following information:

• errorType: Indicates the error type. There are source errors including AJAX errors, console errors, and syntax errors.

• pageLocation: URL of the page visited by the user.

• title: Title of the page visited by the user.

• browser: Browser type of the user.

• borwserVer: Browser version of the user.

• os: OS type of the user device.

• osVer: OS version of the user device.

• device: Type of the user device.

• host: Domain name of the visited server.

• userAgent: User-Agent string received from the user browser.

• message: Error message.

• stack: Error stack information. The error stack basically contains obfuscated file names, lines, and columns.

Source map uploading and error code provision

If the released frontend code is obfuscated or compressed, it is difficult to provide the collected browser error's stack information at an actual code level. You can access the file or code line that caused the browser error through the source-map built at the time of releasing the frontend code.

1. In the Exception stack column, select Analysis.

   

2. If the window in which the error stack information for the selected error log is displayed appears, select Upload.

   

3. Load the source map for the code stack.

By comparing obfuscated stack information with JavaScript source map, you can see the code where the actual error occurred.

AI Error Stack Analysis

Beta

Click the Error Stack Analysis button in the error stack area to have AI automatically analyze error stacks, environment information (browser, OS, device), user behavior logs, and error statistics. It identifies the root cause and impact scope of errors, and suggests solutions.

Analyze

1. Go to Analysis > Error Tracking.

2. Select an error from the error list to open the error detail view.

3. Click the Error Stack Analysis button in the error stack area.

Analysis results

AI collects and analyzes the following data. Available data may vary depending on project settings and error conditions.

Analysis targets

Data	Description
Error stack	Uses restored stack frames if a source map is available, otherwise uses obfuscated stack information.
Environment info	Uses browser, OS, device, and screen size information included in error logs.
Error statistics	Aggregates occurrence counts by page, browser, OS, and device based on the error date.
Session logs	Collects user behavior logs before the error (page navigation, clicks, failed API calls, etc.).

Result structure

The analysis results consist of the following 4 sections:

• Summary: Summarizes the key details of the error in 2-3 sentences.

• Cause Analysis: Classifies and displays error causes by severity (High, Medium, Low).

  Severity	Criteria
  High	Unhandled exceptions causing app crashes, data loss, security vulnerabilities
  Medium	Impacts user experience but workarounds exist
  Low	Minor issues, warnings, cosmetic errors

• Impact Scope: Displays the affected browsers, OS, pages, devices, and occurrence frequency.

• Resolution: Provides action items by priority along with code fix examples.

  Priority	Criteria
  High	Immediate fix required — affects core features or a large number of users
  Medium	Early fix recommended — impacts user experience
  Low	Improvement recommended — minor enhancements

Note

• The analysis results are generated by AI and may differ from actual conditions. Use them as reference material.

• If a source map is uploaded, the analysis uses the restored stack information.

• Available only in SaaS environments.

• Member role or above is required.

Searching by filter the error data

You can search the errors by filtering based on the data included in the browser errors.

1. In the left panel of the screen, select a desired browser error item for filtering.

2. If the sub list appears, select a desired item. You can also search if the list is too many.

It displays a list of browser errors corresponding to the selected item.

Table Column Settings

Displaying or hiding the table columns

You can display or hide column header items in the browser error list table.

1. Select on the upper right of the table.

2. If the Column settings window appears, select or unselect the desired item in the list on the left.

   You can also hide columns by selecting the button in the list on the right.

3. After all settings are finished, select Confirm. The set content is applied to the table.

Reordering the table columns

You can change the order of column headers in the browser error list table.

1. Select on the upper right of the table.

2. When the Column settings window appears, change the order by dragging the desired items from the list on the right.

3. After all settings are finished, select Confirm. The set content is applied to the table.

Setting to display the table content

You can set the content displayed in the browser error list. It can be used when too much information appears so it is difficult to see, or it is required to add necessary information.

1. Select on the upper right of the table.

2. When the Log view detail setting window appears, set the desired options.

   • Select content or Tag to determine whether or not to display the log content.

   • Tag management: Tags are displayed in the log in the order of addition. The order of tags can be changed by dragging. Disabled tags do not appear in the logs.

3. After all settings are finished, click . The set content is applied to the table.

Note

For more information about Log view detail setting, see the following.