Our next-gen architecture is built to help you make sense of your ever-growing data Watch a 4-min demo video!

Back to All Docs

Error Tracking: User Manual

Last Updated: Sep. 10, 2023

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.

Get Started

Once you have configured and installed our browser SDK, in your Coralogix toolbar, navigate to Explore > Error Tracking.

Error Screen (General)

Get an overview of all of the errors generated from your browser. View the number of errors, number of users affected by each, and filter according to your needs.

The Error Screen includes:

  1. Error Overall Graph and KPIs. This graph presents the error trend in the application, in addition to the overall number of errors and users affected.
  2. 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.
  3. Filters. Refine your view by filtering errors according to particular attributes.
  4. Alerts. Create alerts directly from this screen by clicking CREATE ALERT in the upper right-hand corner.

Specific Errors

Drill-down and investigate a specific error by clicking on an error of interest. The Specific Error Screen includes:

  1. Error Header. A header bar with information about the error selected.
  2. Error Graph. This time series graph presents the frequency of the specific error that has been chosen.
  3. Information Grid.
    • Click on the OVERVIEW tab to acquire additional information surrounding the error, including event ID, type, group by, error status, browser, device type, language, country and labels.
    • Depending on the error type, you will presented with a STACK TRACE tab, DEPENDENCIES VIEW tab, or a RELATED LOGS tab.
      • STACK TRACE allows you to to drill-down into a specific stack trace tab. It is presented when the error is an unhandled exception – an error in a computer program or application when the code has no appropriate handling exceptions.
      • DEPENDENCIES VIEW allows you to visualize all the services in the error flow and pinpoint specific servers that may have caused the error. It presented when a network error has occurred.
      • CORRELATE LOGS enables users to view detailed logs associated with errors, providing additional contextual information to aid debugging.
  4. Similar Errors Grid. View and easily move between identical errors received in a selected time period.

Stack Trace

Drill-down and investigate the stack trace of an error by clicking on the STACK TRACE tab.

Dependencies View

Visualize all the services in the error flow and pinpoint specific servers that may have caused the error by clicking on the DEPENDENCIES VIEW tab.

Correlate Logs

View detailed logs associated with errors, providing additional contextual information to aid debugging by clicking on the CORRELATE LOGS tab.

Additional Resources

DocumentationReal User Monitoring
Error Tracking
Browser SDK Installation Guide

Support

Need help?

Our world-class customer success team is available 24/7 to walk you through your setup and answer any questions that may come up.

Feel free to reach out to us via our in-app chat or by sending us an email at [email protected].

On this page