Releases
A release is the version of your application that sent an event, such as 1.4.0 or [email protected]. Tag your events with one and Bugtail can tell you how each version held up.
Setting the release
Set it once in your SDK, usually from your build or deploy:
- Laravel:
SENTRY_RELEASE=1.4.0in.env. See Laravel. - Other Sentry SDKs: the
releaseoption ininit(). - OpenTelemetry: the
service.versionresource attribute. - HTTP: a
releasefield on each event.
Use the same value everywhere a release is named: in the SDK, and when you upload source maps.
What a release gives you
- Where an issue started. Each issue records the release it was first seen in.
- New issues per release. The Releases page counts the issues each version introduced.
- Regressions. A resolved issue that happens again is marked Regressed, with the release it came back in.
- Muting until the next deploy. Mute an issue until the next release and it returns only when a different release reports it.
- Readable browser stack traces. Source maps are matched to events by release.
Crash-free rate
SDKs that track sessions, such as the browser and mobile SDKs, report every session and how it ended. The Releases page shows per release:
| Column | Meaning |
|---|---|
| Crash free | The share of sessions that did not end in a crash. |
| Sessions | How many sessions this release had. |
| Crashed | Sessions that ended in a crash. |
| Errored | Sessions that had an error but did not crash. |
| New issues | Issues first seen in this release. |
Crash free counts sessions, not people: somebody who crashes three times weighs three times. Sessions without a release are not counted, and sessions are never sampled, whatever your sample rate.