Error capture, grouping & triage
How this is scored
What happens to an exception or crash: SDKs for the languages, frameworks and platforms a team runs (PHP and Laravel, JavaScript in the browser and Node, Python, Ruby, Java, .NET, Go, iOS, Android, Flutter, React Native), stack traces with source maps and symbolication, context (request, user, breadcrumbs, environment, local variables), grouping and custom fingerprints, deduplication, issue states (resolved, ignored, regressed), releases and deploy tracking, suspect commits, crash-free sessions and users for mobile apps, and search and filters over issues.
0 — Catches no application errors or crashes; a log viewer or an external check only.
3 — Errors from one or two platforms arrive with a stack trace and are grouped; context, issue states, releases and source maps are basic or not described.
5 — SDKs for the common web and backend platforms, stack traces with source maps, request and user context and breadcrumbs, automatic grouping with issue states and regression detection, release and deploy tracking, and issue search and filters.
8 — SDKs across backend, frontend and mobile with symbolication documented, custom fingerprinting and merge or split of issues, suspect commits or code owners, crash-free users and sessions, local variables or source context per frame, and every SDK documented with its configuration options.
10 — Error tracking a large engineering organisation standardises on: every platform it runs covered with parity stated, grouping rules editable and explained, release health with adoption and regression per version, and the full issue lifecycle reachable by API.
The SaaS CTO
Sentry SDK compatibility means my Go, Python and TypeScript services keep their instrumentation with a DSN change, and the core capture is strong: stack traces centred in the UI with local variables and source context, sourcemaps resolved through debug IDs and artifact bundles, request, header, environment and custom context, issue states with regression detection, and grouping documentation deeper than most vendors — custom fingerprinting with the default key, normalization of UUIDs, emails, IPs and numbers, and a grouping tab that explains the key. I found no public information on suspect commits tying a regression to the change that caused it, on merging or splitting issues, on mobile symbolication and crash-free sessions, or on breadcrumbs, which is where a large team would feel it. 2 3 12 13 14