Features
One error thrown a thousand times by a single bot and one error hitting a thousand customers are different problems. Identify users in the SDK and Buglapse counts and lists the people behind every issue.
User tracking
Every issue shows the number of distinct users it touched, next to the number of events — the first thing to look at when choosing what to fix.
Open a user to see their recent errors and traces. When a customer writes to support, you can see what went wrong for them before asking.
Use the user filter in search to find everything a specific account ran into.
Only the fields you pass to the SDK are stored. Secrets are masked on the server, and IP addresses can be hashed on plans with advanced data scrubbing.
How it works
Pass an id, and optionally an email, a username or a name. Every field is optional.
Calling setUser again merges into what is already known instead of replacing it, so an email can be added later.
Issues show their affected users, and the Users page lists everyone the project has seen, most recently active first.
import { setUser } from '@buglapse/browser'
setUser({ id: user.id, email: user.email })In detail
From the moment setUser is called, the user is attached to every event sent afterwards: errors, logs, spans and sessions. Buglapse matches events to the same person by id first, then by email. Extra fields you pass, such as a plan or a company name, are kept and shown on the event. In Node.js a user can be set for a single request, so concurrent requests never mix their users up.
Server-side scrubbing masks passwords, tokens, card numbers and keys in every event before it is stored, whichever SDK sent it. A project can add its own sensitive field names and mark fields that must never be scrubbed. The user id, email, username and name are the identifiers Buglapse relies on and are kept as sent — so pass an internal id rather than an email if you would rather not store personal data.
| Free | Pro | Team | |
|---|---|---|---|
| Errors & issues | 14 days | 30 days | 90 days |
| Custom data scrubbing rules, IP hashing | Not included | Included | Included |
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 trackingWatch what the user saw before the error, with inputs masked by default.
Learn more: Session replayCrash-free sessions and users per release, and the new issues every deploy brought.
Learn more: Release healthCreate a project on the free plan and send your first event in a couple of minutes.
Still have questions? Email hello@buglapse.com