Exception, Error & Issue Tracking

Examples: Sentry, Rollbar, Bugsnag, TrackJS

LogRocket incorporates the things users like about exception, error, and issue tracking tools, and eliminates their drawbacks:

• Session replays provide the full context behind an error
• LogRocket's Galileo AI cuts through the noise to identify the true user-impacting issues
• Product analytics assess which issues are dragging down your key metrics

What is Exception, Error & Issue Tracking?

Exception, error, and issue trackers are built for a specific use case: your application hit an unexpected situation, and you'd like to be notified about it ASAP. These solutions are alerting tools first and foremost, and have two significant drawbacks, especially on the front end:

• Noisy: They alert every time something unexpected happens in your app. As a result, these tools are noisy and full of false positives - often sending hundreds or even thousands of alerts daily. To make matters worse, every alert is treated the same, no matter the severity. An image that fails to load receives the same treatment that causes your app to crash. This gives you two options: spend hours triaging errors to find what really matters, or start ignoring most alerts at the risk of missing something important.
• Can't provide the full picture: Investigating back-end errors is usually fairly straightforward. On the front end, things aren't so simple. The average web application runs in over 15 different browsers, across hundreds of device types. State can be highly complex, coming from memory, local storage, local databases, service workers, and APIs. A web app must be robust to connectivity issues and cross-browser differences. Unlike the back end, it can be tricky to gauge the impact on the front end from an error message alone.

How is LogRocket Different?

📘

What's the difference between exceptions, errors, and issues?

Exceptions, errors, and issues all sound similar and are sometimes used interchangeably, but there are a few important differences to note, especially from a LogRocket perspective.

• Exceptions and Errors both refer to unexpected behavior with an application's code and are therefore always technical. Some errors and exceptions are noticed by users and affect their experience, while others can go unnoticed by end users.
• Issues, on the other hand, are always user impacting and affect the app experience in some way. Errors and exceptions can be issues if they cause problems for end users, but not all errors and exceptions are issues. Conversely, issues can be caused by things other than errors and exceptions, such as poor application design.

LogRocket is designed to solve the problems associated with traditional exception and error tracking tools. Using the context provided by session replay, LogRocket can tell you whether an error impacts a user's experience and what steps are needed to reproduce the problem. Additionally, LogRocket's Galileo AI is able to watch every error, exception and issue for you, using contextual behavioral signals and historical data to assess severity. It notifies you of only the things that you need to care about so you don't need to worry about missing anything in the noise.