Skip to content

Umami 3.5 adds browser error tracking

Uncaught exceptions and unhandled rejections, grouped into issues with stack traces and occurrence counts, in the analytics tool you may already be self-hosting.

Source: GitHub

Umami shipped v3.5.0 yesterday, and the headline is browser error tracking sitting next to the analytics rather than in a separate product.

Turn it on with data-errors="true" on the tracker script and it captures uncaught exceptions and unhandled promise rejections automatically. Handled errors go in through umami.captureException(). Errors are grouped into issues carrying stack traces, occurrence counts and session details, and you can resolve, ignore or reopen them, or filter by release, environment, browser and page path.

The same release adds previous and next replay controls with arrow-key shortcuts, tracker configuration through window.umamiConfig, optional client-provided session salts with hourly to monthly rotation behind ENABLE_CLIENT_SALT, and TRUSTED_PROXIES for client IP detection behind more than one proxy.

Why it matters: for a small site this is one fewer service to run. Analytics and error monitoring are usually two vendors, two scripts and two bills, and a self-hosted box that does both covers a lot of what most projects actually need. I run Umami on this site, so this is one I will be turning on.

The caveat: issue grouping, release tagging and source maps are where error trackers earn their keep, and a first release is not going to match a mature one. Treat it as enough to catch what is breaking, not as a Sentry replacement on day one.

Share

Related reading

More from The Wire

All briefs