This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!
This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Overview

Error Tracking processes errors collected from browser and mobile Datadog Log SDKs. Whenever an error containing a stack trace is collected, Error Tracking processes and groups it under an issue, which is a grouping of similar errors.

An essential attribute for log errors is the stack trace in a log’s error.stack. If you are sending stack traces to Datadog but they are not in error.stack, you can set up a generic log remapper to remap the stack trace to the correct attribute in Datadog.

Your crash reports appear in Error Tracking.

Setup

If you have not set up the Datadog Browser Logs SDK yet, follow the in-app setup instructions or see the Browser Logs setup documentation.

  1. Download the latest version of the Logs Browser SDK. Error Tracking requires at least v4.36.0.

  2. Configure your application’s version, env, and service when initializing the SDK. For example, with NPM:

    import { datadogLogs } from '@datadog/browser-logs'
    
    datadogLogs.init({
      clientToken: '<DATADOG_CLIENT_TOKEN>',
      site: '<DATADOG_SITE>',
      service: '<MY_SERVICE>',
      env: '<MY_ENV>',
      forwardErrorsToLogs: true,
      sessionSampleRate: 100,
    })
    
  3. To log a caught exception yourself, you may use the optional error parameter:

    try {
      throw new Error('wrong behavior');
    } catch(err) {
      datadogLogs.logger.error("an error occurred", {usr: {id: 123}}, err);
    }
    

Note: Error Tracking only considers errors that are instances of Error.

If you have not set up the Datadog Android Logs SDK yet, follow the in-app setup instructions or see the Android Logs setup documentation.

  1. Download the latest version of the Datadog Android SDK for Logs.

  2. Configure your application’s version, env, and service when initializing the SDK.

  3. To log a caught exception yourself, you may optionally use:

    try {
      doSomething()
    } catch (e: IOException) {
      logger.e("an exception occurred", e)
    }
    

If you have not setup the Datadog iOS Logs SDK yet, follow the in-app setup instructions or see the iOS Logs setup documentation.

  1. Download the latest version of the Datadog iOS SDK for Logs.

  2. Configure your application’s version, env, and service when initializing the SDK.

  3. To log a caught exception yourself, you may optionally use:

    do {
      // ...
    } catch {
      logger.error("an exception occurred", error)
    }
    

If you have not setup the Datadog Kotlin Multiplatform Logs SDK yet, follow the in-app setup instructions or see the Kotlin Multiplatform Logs setup documentation.

  1. Download the latest version of the Datadog Kotlin Multiplatform SDK for Logs.

  2. Configure your application’s version, env, and service when initializing the SDK.

  3. To log a caught exception yourself, you may optionally use:

    try {
      doSomething()
    } catch (e: IOException) {
      logger.error("an exception occurred", e)
    }
    

Further Reading

PREVIEWING: rtrieu/product-analytics-ui-changes