Error tracking
An app's errors land next to its status page and its alerts. Any Sentry SDK sends to a StatOSS DSN; moving is changing one line. 5,000 errors a month on Free, 50,000 on Hobby, 500,000 on Pro.
import * as StatOSS from "@statoss/sdk";
StatOSS.init({
dsn: "https://<key>@ingest.statoss.com/<app number>",
environment: "production",
});The DSN
An app made under Apps has a DSN of the form https://<key>@ingest.statoss.com/<app number>. Any Sentry SDK takes it where Sentry's DSN goes.
SDKs and CLI
@statoss/sdk for JavaScript and TypeScript, the Python statoss package over sentry-sdk, any Sentry SDK, and sentry-cli or npx @statoss/cli for releases and source maps.
Issues
Events group into issues by fingerprint, then by exception type and in-app frames. Resolve, resolve in the next release, archive, assign, merge; a later event reopens an issue as regressed.
Alert rules
On Hobby and Pro an app's rules open on-call alerts: new issue, regression, escalation, or N events in a window, filtered by level, environment, release and category. On Free, new and regressed high-priority issues are emailed to the owner, 25 a month.
Your own levels and categories
An app defines levels, categories and fields in code with @statoss/sdk; a wrong name fails to compile.
Limits and price
Free: 5,000 errors and messages a month, kept 30 days. Hobby: 50,000, kept 30 days. Pro: 500,000, kept 90 days. Past the allowance events are answered 429, as Sentry answers. Included in every plan; the pricing page has the rest.