Error monitoring
Crashes and errors from your live product, captured with enough detail to fix them and reported to the team before users have to complain.
Updated October 2026 · with examples from our own builds
What does error monitoring mean in practice?
Tools such as Sentry collect errors from apps and servers as they happen: what broke, on which device or route, in which build and how often. With source maps uploaded, they point to the exact line in the original code.
Monitoring is how you hear about problems first. Without it, the first sign of a crash is a bad review or a support email.
The monitoring account belongs to the product's owner. At a handover it should move to your organisation, and someone should check that the live build reports to the new account rather than the old one.
Error monitoring at a glance
- Captures
- Crashes and errors with device, route and build
- Needs
- Source maps for readable mobile and web errors
- Ownership
- The account should sit in your organisation
Where has error monitoring come up in our builds?
In August 2026 we moved error monitoring to Trainr's own Sentry organisation, then pulled the JavaScript bundle out of the built app and searched it: the new DSN once, the old one nowhere.
A broken audit chain puts a SEV-1 banner across the admin dashboard, and three failed off-site shipments in a row raise a critical alert.
A report of emails that wouldn't open was traced through the production log, a TypeError and request lines showing responses that never finished, to one bug in the mail mapper.
Common questions about error monitoring
Will error monitoring slow my app down?
Not noticeably when configured normally; reports are small and sent in the background. Strip noisy debug logging from release builds so the useful errors stand out.
Who should receive error alerts?
Whoever can act on them during the hours you have promised to cover, with a clear rule for which errors wake someone up and which can wait until morning.
Related terms
Sources
Planning a product and not sure where error monitoring fits? Ask us, or browse all 116 terms in the glossary.