In order to understand what happened in your application before each error, it can be helpful to leave short log statements that we call breadcrumbs. A configurable number of breadcrumbs are attached to each error report to help diagnose what events led to the error.
This documentation is for version 7+ of the BugSnag JavaScript notifier. If you are using older versions, we recommend upgrading to the latest release using our Upgrade guide. Documentation for the previous release can be found on our legacy pages.
Breadcrumbs for common actions and device changes are captured by default. This can be controlled using the enabledBreadcrumbTypes
configuration option.
Append manual breadcrumbs with a message via the Bugsnag
client:
Bugsnag.leaveBreadcrumb('App loaded')
Bugsnag.leaveBreadcrumb('User clicked a button')
BugSnag will keep track of the time and order of the breadcrumbs and show them on your dashboard.
Additional data can be attached to breadcrumbs by providing the additional metadata
argument. Metadata will be presented on the BugSnag dashboard alongside the breadcrumb name and type:
var metadata = {
from: 'moka',
to: 'french press'
}
Bugsnag.leaveBreadcrumb('Preference updated', metadata, 'state')
Breadcrumb “types” can be used to differentiate different types of events, such as user activity and changes in application state. See the breadcrumb types
list for a complete list of the breadcrumb types available. Your breadcrumbs will not be affected by the enabledBreadcrumbTypes
configuration option.
You can register a callback that is executed each time a breadcrumb is captured using addOnBreadcrumb
.
This can be helpful if you wish to filter out certain automatic breadcrumbs from your application or amend
the data contained within them.
Bugsnag.start({
onBreadcrumb: function (breadcrumb) {
if (breadcrumb.type === 'navigation') {
if (breadcrumb.metadata.to === '/home') return false
breadcrumb.metadata.to = stripQueryString(breadcrumb.metadata.to)
}
}
})
If log
breadcrumbs are enabled, do not log within an onBreadcrumb
callback to avoid an infinite loop.
We recommend adding callbacks through the onBreadcrumb
configuration option to ensure that it is registered as soon as BugSnag starts. However, the following methods are provided to allow callbacks to be added and removed whilst the application is running:
var cb = function (breadcrumb) { /* ... */ }
Bugsnag.addOnBreadcrumb(cb)
// ...
Bugsnag.removeOnBreadcrumb(cb)
Breadcrumb
objectThe following information is available on a Breadcrumb
object, the representation of breadcrumb information available in an onBreadcrumb
callback.
property | type | description |
---|---|---|
message |
String |
The description of the breadcrumb |
metadata |
Map |
Diagnostic data relating to the breadcrumb |
timestamp |
Date |
The timestamp that the breadcrumb was left |
type |
String |
The type of breadcrumb left |