--- title: 'Error tracking: user manual' description: As part of our Real User Monitoring (RUM) toolkit, Coralogix offers multi-faceted Error Tracking. Designed to help web application owners and developers gain insights into errors occurring within their users' browsers, this tool allows you to effectively capture and analyze frontend errors to optimize application performance and enhance the overall user experience. This user manual demonstrates how to engage with our RUM UI to get the most out of our Error Tracking features. url: https://coralogix.com/docs/user-guides/rum/product-features/error-tracking-user-manual/ product: rum feature: Error Tracking feature_id: rum-error-tracking feature_identifier: rum/rum-error-tracking last_updated: '2026-11-12' --- # Error tracking: user manual As part of our [Real User Monitoring](https://coralogix.com/docs/user-guides/rum/getting-started/real-user-monitoring.md) (RUM) toolkit, Coralogix offers multi-faceted Error Tracking. Designed to help web application owners and developers gain insights into errors occurring within their users' browsers, this tool allows you to effectively capture and analyze frontend errors to optimize application performance and enhance the overall user experience. Get an overview of all errors generated from your browser or view related errors in a consolidated manner. You can view errors as individual errors (**Error Screen**) or aggregated into groups (**Error Template View**). This user manual demonstrates how to engage with our RUM UI to get the most out of our **Error Tracking** features. ## Access the Error Tracking view Once you have [configured and installed our browser SDK](https://coralogix.com/docs/user-guides/rum/sdk-installation/javascript/npm-browser.md), in your Coralogix toolbar, hover over **RUM**, then select **Error Tracking**. ## View and explore errors By default, the **Error Tracking** view opens in the **Errors** panel, which lists all captured browser errors. Use the Errors panel to see every individual error generated by your browser, along with the number of affected users and total occurrences. You can filter results, adjust columns, and create alerts directly from this screen by selecting **Create Alert**. ### Display The Error Screen includes: 1. **Filters.** Refine your view by filtering errors according to particular attributes. 2. **Error Overall Graph and KPIs**. This graph presents the error trend in the application and the overall number of errors and users affected. 3. **Error Grid.** Use the error table grid to view error information, row by row. Modify columns and the information presented based on your specific interests. [![Coralogix Error Tracking view listing errors with their platform, count, and last-seen columns](/docs/assets/images/1-1-2-dca0e634c8c507f3c7d7e1e806be579a.webp)](https://coralogix.com/docs/assets/images/1-1-2-dca0e634c8c507f3c7d7e1e806be579a.webp) ## Group related errors In addition to a granular view of all errors, take advantage of our **Error Template** view, where similar errors with shared attributes are grouped into a single template for quick and easy analysis. Find out more [here](https://coralogix.com/docs/user-guides/rum/product-features/error-template-view.md). ## View error details Select any error in the **Error Tracking** table to open its info panel and analyze it while keeping the full error list in view. The info panel displays all details previously found in the dedicated error view, now organized into collapsible sections. At the top of the panel, view key metrics for the selected error: * **Users affected**: Total number of unique users who encountered the error. * **Error count**: The number of times this error occurred during the selected time range. * **Sessions with errors**: The number of recorded sessions that include this error. Each metric includes a more actions menu to **View Query** in DataPrime or **Copy Query**, so you can open or modify the query directly in [Explore](https://coralogix.com/docs/user-guides/data_exploration.md) or [Custom Dashboards](https://coralogix.com/docs/user-guides/custom-dashboards/introduction.md) for deeper analysis. ### Overview The **Overview** section provides essential context and attributes for the selected error.
The following image shows an example overview panel with key attributes such as **event ID**, **status**, and environment details. [![Error Tracking overview panel with the error summary, affected sessions, and platform breakdown](/docs/assets/images/Error-Tracking-Overview-copy-46093aa23888e96ba8e429ceb33e17da.webp)](https://coralogix.com/docs/assets/images/Error-Tracking-Overview-copy-46093aa23888e96ba8e429ceb33e17da.webp) Provides essential context and attributes for the selected error, including: * **Event ID** and error type * **Status** and group * **Browser**, **device type**, and **country** * User labels and metadata ### Stack trace When available, the **Stack Trace** section shows the code-level traceback for unhandled exceptions. Use this to pinpoint the exact source or function that triggered the error. The following image shows a sample stack trace view within the info panel. [![Stack trace showing code-level traceback for an unhandled exception](/docs/assets/images/Error-Tracking-Stack-Trace-copy-20884a144719682a5f5a65959a45cc3d.webp)](https://coralogix.com/docs/assets/images/Error-Tracking-Stack-Trace-copy-20884a144719682a5f5a65959a45cc3d.webp) ### Breadcrumbs The **Breadcrumbs** section lists events leading up to the error, helping you understand the user’s journey before the issue occurred. Each event includes its **timestamp**, **type**, **severity**, and **URL**, with filtering and search controls to refine the view. The following image shows a breadcrumbs list with event types, timestamps, and severity indicators. [![Breadcrumbs section showing user actions and event sequence before an error](/docs/assets/images/Error-Tracking-Breadcrumbs-00edef82451f0b89a7288a8c9ba7a727.webp)](https://coralogix.com/docs/assets/images/Error-Tracking-Breadcrumbs-00edef82451f0b89a7288a8c9ba7a727.webp) ### Correlated logs The **Correlated Logs** section surfaces logs tied to the same session and context, providing deeper diagnostic data for root-cause analysis. You can open any correlated log query directly in **Explore** by selecting **View query in DataPrime** or copy it for use in a custom visualization. To ask Olly about a specific log, hover its row and select **Add to Olly context** (the Olly icon). Olly opens with the log attached as data context. Select the icon again to remove it. On accounts that store RUM data as RUM events, the row is attached as a RUM event rather than a log. See [Page and data context](https://coralogix.com/docs/user-guides/olly/olly-chat.md#page-and-data-context). The following image shows correlated logs with options to view or copy their DataPrime queries. [![Correlated logs section showing query options for Explore or Custom dashboards](/docs/assets/images/Error-Tracking-Correlated-Logs-copy-2c286160732e85e4300be63f3ef1933e.webp)](https://coralogix.com/docs/assets/images/Error-Tracking-Correlated-Logs-copy-2c286160732e85e4300be63f3ef1933e.webp) ### Navigation * Switch between error entries in the table to update the info panel instantly without leaving the main screen. * To close the panel, select **Close** in the top-right corner or select anywhere outside the drawer. ## Copy a prompt for your AI agent Hand an error to a coding agent such as Claude Code, Cursor, Codex, or GitHub Copilot in one step. **Prompt for AI agents** copies the error's context as Markdown that you can paste into the agent, a ticket, or a Slack message. 1. In the [Error Tracking view](#access-the-error-tracking-view-cx-general-error), open an error from the **Templates** or **Errors** view. 2. In the error header, select **Prompt for AI agents**. A confirmation appears when the prompt is copied. 3. Paste the prompt into your AI agent. [![The Prompt for AI agents menu in the RUM error header, with Copy error ID, Copy error link, and Give your agent Coralogix access](/docs/assets/images/prompt-for-ai-agents-1dd649cfede5dce0f0a20ec6bb611ab5.webp)](https://coralogix.com/docs/assets/images/prompt-for-ai-agents-1dd649cfede5dce0f0a20ec6bb611ab5.webp) Select the arrow next to **Prompt for AI agents** for more options: * **Copy error ID**: Copies only the error's ID. * **Copy error link**: Copies only the link to the error in Coralogix. * **Give your agent Coralogix access**: Opens the dialog for connecting your agent to Coralogix through the Coralogix CLI or MCP server. ### What your agent receives The prompt is headed with the error message, followed by the details below. Fields with no value are left out. * The error type and message * Application, version, platform, and environment * Impact: the number of errors, users, and sessions in the selected time range, and the version where the error was first seen * The most likely location: the first stack frame in your own code, outside `node_modules` * The release commit and repository * The template ID (or the event ID when the error has no template) and a link back to the error in Coralogix * The stack trace, showing your app's own frames mapped with source maps * The source lines around the failing line, when source maps provide them With this context, the agent can find the failing line in your repository and investigate the cause without you copying details by hand. The prompt holds facts only, with no instructions, so you decide what to ask the agent to do. An agent with Coralogix access can also look up the error by its template ID or link to pull more data. Network and log errors have no stack trace, so their prompts don't include the stack trace, location, or release details. Without [source maps](https://coralogix.com/docs/user-guides/rum/cli/rum-cli.md), the stack trace shows the minified frames as recorded. Emails, JWTs, bearer tokens, and token-like URL parameters are masked, and user names, IDs, IP addresses, and locations are never included. ## Alert on an error [![Coralogix alert configuration opened from an error in Error Tracking](/docs/assets/images/RUM-Alerting-1024x829-59bec68b9b65667042570bdcbf5b869d.webp)](https://coralogix.com/docs/assets/images/RUM-Alerting-1024x829-59bec68b9b65667042570bdcbf5b869d.webp) Alerting refers to the practice of setting up automated notifications or alarms that trigger when certain predefined conditions or thresholds are met. These conditions can be related to the performance, health, or behavior of the systems, applications, or infrastructure being monitored. The main purpose of alerting is to promptly notify DevOps teams and developers – when something unusual or problematic occurs, so you can take appropriate actions to resolve the issue before it escalates. For more detailed information on Coralogix Alerts, see [Getting Started with Coralogix Alerts](https://coralogix.com/docs/user-guides/alerting/introduction-to-alerts.md). Coralogix enables you to create [alerts](https://coralogix.com/docs/user-guides/alerting/introduction-to-alerts.md) directly from the Error Tracking screen, with several different available options for alert creation. * **Create a custom alert directly from the Error Tracking screen.** Select the **Create Alert** in the right-hand side of the screen to open the alert creation panel. * **Create an alert from a specific error.** Select on the left-hand side of the error, then select **Create Alert**. The alert creation panel opens with the specified error details already in the query. * **Create an alert from a specific template.** Select on the left-hand side of the template number and select **Create Alert**. The alert creation panel opens with the specified template details already in the query. * **Create an alert from a template or error drill-down page.** In the error header, select **Actions** > **Create Alert**. The alert creation panel opens with the specified error or template details already in the query. [![The created alert listed alongside the error it tracks](/docs/assets/images/2-1-1024x690-1cfbf4dfed084f2062188689943cb08e.webp)](https://coralogix.com/docs/assets/images/2-1-1024x690-1cfbf4dfed084f2062188689943cb08e.webp) ## Related resources [Upload iOS debug symbols](https://coralogix.com/docs/user-guides/rum/cli/uploading-debug-symbols-ios.md)[RUM saved views](https://coralogix.com/docs/user-guides/rum/product-features/rum-saved-views.md)[Explore screen](https://coralogix.com/docs/user-guides/data_exploration.md)