Bugsnag vs ESPHome

BugSnag ships one dated digest a month, and for the past six the bulk of the content has been Performance, not error monitoring: span groups, session windows, pre-main iOS start times, and CPU/memory/rendering metrics. Error monitoring still gets work, but it reads as maintenance — filter operators, App Hang detection, HTTP error capture — while the new surface area lands in the Performance product. Flutter has been pulled up to iOS/Android parity over two consecutive releases. A self-hosted MCP server sits alongside all of it, gaining OAuth and write actions rather than staying a read-only lookup.

The product is converging on a single app-health telemetry store where an error, a span, a session, and a device metric are all queryable against each other — Correlated Events in April was the clearest statement of that, and July's per-session aggregated CPU and memory extends it to resource cost. The SDK is becoming the control surface: developers define their own session windows and delivery strategies rather than accepting BugSnag's defaults. The MCP work is the quieter arc, moving from token-based reads to OAuth logins and mutating actions like snoozing errors and linking Jira issues.

Expect the Sessions tab to gain the same correlation treatment errors got — jumping from a session window straight to the events and spans inside it. The MCP server is the thing to watch: it has been given auth and write actions in consecutive digests, which points at more triage operations exposed to agents next.