When debugging an issue in a UI, it can be useful to know what events occurred in the build up to the error being thrown. Breadcrumbs are a time-ordered list of events in your application, that is filled as a user traverses your application, and is sent along with a
Span whenever an error is caught by the library. This allows you to gather information that is useful for reproducing tricky-to-debug errors by re-tracing a user's path through your application.
By default, no breadcrumbs are tracked, but it's really easy to track your own. Alternatively, you can use one of our breadcrumb plugins to automatically collect some types of breadcrumbs.
Wherever an interesting event, operation or state change occurs in your app, you can leave a breadcrumb like so:
When an error is thrown and caught by the AppSignal library, or a
Span is passed to
appsignal.send(), the current list of breadcrumbs is added to the current
Span and sent to the server. The list of breadcrumbs is then emptied.
|category||String||Category to label the event under|
|action||String||Contextual information related to the event|
|message||String||(optional) A log message or other string to send to AppSignal|
||(optional) An object of metadata related to the event|
There are a number of plugins available to enable automatic collection of breadcrumbs, and more will be added as time goes on:
Have a good idea for a breadcrumbs plugin? Get in touch with us or leave an issue on Github!