Documentation
Breadcrumbs
When an error lands, breadcrumbs show what happened right before it.
What they are
A breadcrumb is one step in a short trail: a navigation, an HTTP call, or a custom label you send. The trail is attached to the error event and shown on the issue.
route · pathname
/settings/billing
request · API [GET]
/api/plans · 200 · 142ms
common · action
click upgrade
request · API [POST]
/api/checkout · 500 · 890ms
Example trail on an issue.
Types
| Type | Use for | name | value |
|---|---|---|---|
route | navigation | e.g. pathname | /checkout |
request | HTTP calls | e.g. API [POST] | URL; optional status and duration (ms) |
common | anything else | short label | detail |
On an issue
Each event can carry up to 24 breadcrumbs (oldest drop first). Use them to see the path to the crash — which page, which request failed, what the user did last.
Keep values small: paths and short labels, not request bodies or tokens.
In the SDK
Network fetch / XHR are recorded automatically after init. Routes and custom
steps need addBreadcrumb. API and hooks:
SDK → Breadcrumbs.