Concepts

App

One app your team ships, as Athar knows it. Each app has its own ingest keys: the SDK sends with one of them. Revoking a key stops every SDK that uses it at once. Deleting an app deletes its keys, issues, events, releases and product events.

Event and issue

An event is one error, as one device sent it. Events group into issues by where they come from, so one bug is one issue however many times it happens. The Issues list shows open issues first, the most recent at the top.

An issue is open, resolved or ignored. A resolved issue that happens again regresses: it opens again, and shows as the same issue.

Fatal and non-fatal

A fatal event is a crash. The SDK writes it down and sends it on the next launch, with the version that crashed. A non-fatal event is an error your app survived: a caught exception you reported, or a failed call. Both are grouped and analysed the same way.

Release and environment

Every event carries the release (4.2.0+420) and the environment (production, staging) your app sent it with. An issue knows its first and its last release.

Analysis

Each new or regressed issue gets an analysis: what went wrong, where, and a step-by-step plan to fix it, shaped to paste into a coding agent. Each analysis says how sure it is, and says so plainly when it can’t tell. It is a model’s reading of the stack and the events: check it before you act on it.

Tracker

GitHub, Linear, Jira Cloud and Notion. An issue sent to a tracker keeps its status in step both ways: close the ticket and the issue resolves; the issue regresses and the ticket reopens. An export rule sends issues by themselves once they reach a number of events.

Product events

What your app logs with ErrorReporting.track, newest first, under Product events. Search them by the exact event name.

Usage

Your plan caps the errors counted each month. Past the cap, errors are dropped and counted, never silently: Usage shows each one. The count starts again each month.