# Capturing errors

Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Frum%2Fsdk-features%2Fcapturing-errors.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Frum%2Fsdk-features%2Fcapturing-errors.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

## Overview[​](#overview "Direct link to Overview")

The Real User Monitoring (RUM) **Browser SDK** collects front-end errors and provides detailed information, such as error messages and stack traces, whenever available. This ensures you can track and analyze critical issues affecting your web application’s performance.

## Capturing handled errors[​](#capturing-handled-errors "Direct link to Capturing handled errors")

In addition to automatic tracking, you can manually capture handled and other untracked errors using the following:

```
try {

  // Some code that might throw an error

} catch (error) {

  CoralogixRum.captureError(error);

}
```

## Capturing unhandled errors[​](#capturing-unhandled-errors "Direct link to Capturing unhandled errors")

The Coralogix SDK automatically captures and reports any unhandled errors that occur in your application's runtime, without requiring additional configuration. Typically, unhandled errors are those not caught by a `try/catch` block.