This topic explains how to use LaunchDarkly’s observability features to understand and view errors in your application. The Errors view displays a list of recorded errors.
To instrument your application to capture errors, read the documentation on Observability SDKs. The functionality is available through plugins to the LaunchDarkly JavaScript SDK.
To view errors, open the Telemetry section and navigate to the Errors list.
To view details about a specific error, click the error in the list. The error details page appears. The page displays details about how many times the error has occurred, how many users have been affected, and when the error was first and most recently observed. The page opens to the Instances tab.
Use this tab to get an overview of the error’s impact and see stack traces on per-instance occurrences. You can see details about a specific occurrence of an error, like what browser the user encountered it in, what URL they had loaded when it occurred, and more.
This tab includes a “Stacktrace” section, which LaunchDarkly populates:
ldcli for uploading sourcemaps.
An error’s Metrics tab shows you details about how the error has occurred over time and across different environments. You can see the number of times an error has occurred in a given second, the environments and browsers the error has occurred in, and more.
LaunchDarkly groups errors together based on their error message and stack trace. When your application throws an error, LaunchDarkly finds the closest matching error and adds the new error instance to it.
An error matches if:
A stack frame matches if:
If there is no match with an existing error, LaunchDarkly creates a new error group.
As you review errors, you can change their status.
To change the status of an error:
You can also configure LaunchDarkly to automatically resolve errors that have not appeared for a given time period. To learn how, read Observability settings.
To learn more about the search specification for the errors view, read Search specification.
By default, the observability SDK plugin automatically injects the following attributes to provide additional help with searching for traces:
You can filter out errors that you do not want to view in LaunchDarkly. This is useful for errors that you know are not relevant to your application, or that are not actionable. Filtered errors do not count against your errors quota.
You can set up ingestion filters to manage the number of errors recorded in the following ways:
development environment. For each error LaunchDarkly receives, it makes a randomized decision that results in storing only 1% of those matching errors.You can configure these filters from your project settings. To learn how, read Observability settings.