Features
An error count alone does not say how bad a release is. Sessions give errors a denominator: the share of visits and users that went through without a crash, for every version you ship.
Release health
The share of sessions that did not crash and the share of users none of whose sessions crashed, per project and per release.
Each release page lists the issues first seen in it, with event counters and the commit it was built from — the deploy that broke something is easy to find.
Sessions do not count toward any quota and are never sampled, so the crash-free numbers stay exact however much traffic you have.
When the crash-free rate of the last hour falls below the threshold, the team gets an alert — at most once a day per project.
How it works
The session integration of the browser SDK is on by default, with the script tag and the npm package alike.
Pass a release and an environment to init — a version, a git commit or a build number — so the numbers can be compared between deploys.
Open Sessions for the overall picture and Releases to see every version with its crash-free rate and new issues.
import { init } from '@buglapse/browser'
init({
dsn: 'https://YOUR_PROJECT_TOKEN@app.buglapse.com',
release: 'web@1.4.2',
environment: 'production',
})In detail
The browser SDK tracks one session per visit. It starts when the SDK initializes, survives reloads and new tabs on the same site, and ends after thirty minutes of inactivity. A session is healthy, errored when a handled error was reported, or crashed when an unhandled error occurred. An issue page also shows the share of sessions the issue occurred in since it first appeared, which tells how many visits a single bug really touches.
The release string you set is stamped on errors, logs, spans and sessions. It is the same value that source maps are matched against, so a release page brings together the stability of that version, the issues it introduced and the files that have source maps. The first release of an issue never changes afterwards, which makes it clear where a bug came from even months later.
| Free | Pro | Team | |
|---|---|---|---|
| Sessions (release health) | 7 days | 14 days | 90 days |
| Errors & issues | 14 days | 30 days | 90 days |
FAQ
Still have questions?
Drop us a line — we'll help with setup, plans or self-hosting.
Contact usor email hello@buglapse.com
See also
Every error grouped into one issue with a readable stack trace, breadcrumbs, the steps to the error and the affected users.
Learn more: Error trackingMinified stack traces decoded back to your original files and lines.
Learn more: Source mapsAlerts about new and returning errors, spikes, stability drops and downtime — by email, in Telegram and in MAX.
Learn more: AlertsCreate a project on the free plan and send your first event in a couple of minutes.
Still have questions? Email hello@buglapse.com