Skip to content
Docs menu

Venom Incidents

Error tracking for your own apps in your own Venom Cloud: errors grouped by cause with the release and the flags served, triaged from the keyboard or by an agent.

View .md

Venom Incidents is where the errors from your own apps land. A browser or a Node process sends an error to your Venom Cloud, which groups it with the others that have the same cause. You see one issue with an exact count, the users it touched, the release it started in, the stack (read as your source when you upload source maps) and the feature flags the user was served when it broke.

It is the Errors half of a larger product. Incidents (a timeline, roles, status updates) use the same issues; The add-on is incidents; while the price is not set for your cloud, every organisation has it.

  • Incidents: declare one, roles, a self-filling timeline, status updates for your status page.
  • Errors: the stream, the issue page, states, merging and source maps.
  • The errors SDK and ingest: init, captureException, the wire format, releases from CI.
  • The loop: a spike opens an incident, the flag that caused it is rolled back, an agent gets a Tasks issue.
  • Postmortems: a blameless draft in Notes for every resolved incident.
  • On-call: schedules, overrides, escalation policies and pages.
  • Alert sources: Alertmanager, Grafana or any JSON sender, signed.
  • Alerts: rules for a new issue, a regression, a spike, a threshold or a burning error budget.
  • Build on Venom Incidents: every MCP tool and REST route, the scopes, and a triage loop for agents.

Open it from the rail, or press g e. Projects and environments are Venom Flags': a project made in either product exists in both, and an SDK uses the environment keys you already have.

Page What it shows
/incidents The issue stream for the current project and environment.
/incidents/e/{id} One issue: count, users, release, stack and the flags served.
/incidents/alerts The project's alert rules and their recent hits.
/incidents/quickstart The SDK setup, the CI calls and a curl line to send a test error.
/incidents/inc Incidents, worst severity first.
/incidents/inc/{number} One incident: timeline, roles, likely cause and postmortem.
/incidents/oncall Who is on call, the open pages, schedules, escalation policies and alert sources.
/incidents/settings The loop (automatic rollback, the Tasks team and triage agent), fingerprint rules and releases.

What stays yours

Errors are posted only to the base URL your app gives the SDK, and nothing is sent anywhere else. There is no session replay. Secrets in messages, breadcrumbs, tags and extra context are replaced with [REDACTED:…] before an event is stored, using the same detectors as prompt filters. Full events are kept 30 days; the counts are kept 90.

In this section

  • Errors: Triage your apps' errors: the issue stream and its keys, the issue page, states and regressions, merging, source maps and filing a Tasks issue.
  • Incidents: Declare an incident with a severity and roles, follow a timeline that fills itself with flag changes, releases and alerts, and post status updates that reach your status page.
  • The loop: An error spike opens an incident, Venom ranks what changed, rolls back the flag that did it through Venom Flags (if you allow it), and files a Tasks issue for an agent with the stack and the suspects.
  • Postmortems: A blameless postmortem draft in Notes for every resolved incident, its action items as Tasks issues, an eval case from the regression, and a draft PR with a failing test.
  • Error alerts: Rules that tell you about a new issue, a regression, a spike, a threshold or a burning error budget: the bell, org webhooks and Slack, a dry run over the last 24 hours, and how a hit is decided.
  • On-call: Schedules with layered rotations and overrides, escalation policies, and pages that tell the right person through the bell, a webhook, Slack, SMS and a phone call, and escalate until someone acknowledges.
  • Alert sources: Point Prometheus Alertmanager, Grafana or any JSON sender at a signed URL to page the on-call and, if you want, open an incident.
  • The errors SDK and ingest: Send your app's errors to your Venom Cloud with the dependency-free TypeScript SDK or plain HTTP: init, captureException, breadcrumbs, flags served, releases, grouping and the limits.
  • Migrate from Sentry, or send OpenTelemetry exceptions: Keep your Sentry SDKs and point the DSN at your own Venom Cloud, or export OpenTelemetry exception events with a collector: the DSN, the key, what is kept and what is dropped.