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.
Open Incidents from the rail or press g e. The sidebar has Errors, a Quickstart and Settings. The project switch
in the top bar is Venom Flags' project list.
The stream
One row per issue: its state, title and culprit (the in-app function that threw), a 24 hour sparkline, events, users affected, last and first seen, release and environment. Filter by state (open is unresolved and regressed), environment, assignee and text, and sort by last seen, first seen, events or users. The filters live in the URL, so a view can be shared.
| Key | Does |
|---|---|
j k |
move down and up |
Enter |
open the issue |
e |
resolve (again to reopen) |
i |
ignore (again to reopen) |
a |
assign |
u |
mark unresolved |
/ |
search |
A triage change applies at once and shows a toast with Undo. The same keys work on the issue page, where Escape
goes back to the stream.
The issue page
The header has the state, the level and the assignee, and the actions: Resolve, Ignore, Assign, Merge and Create Tasks issue. Under it, the counts for the last 24 hours and 14 days, then the selected event:
- the stack, in-app frames first with a link to show the library frames. Where the release has source maps, a frame shows your original file, line and the lines around it;
- breadcrumbs, the last 50 things the app did before the error;
- the event's user, URL, tags and the flags it was served.
The side column lists the releases the issue appeared in (with the commit when one is known), the flags that were served across its stored events, tags, merged issues and the activity log. Up to 20 full events are stored per issue and hour, and the counts are exact whatever is stored; the Events list pages through the stored ones.
States
| State | Meaning |
|---|---|
| Unresolved | Open. |
| Resolved | Done. Resolve now, in a named release, or in the next release. |
| Regressed | It was resolved, and happened again where that should not be. |
| Ignored | Hidden from the open stream: forever, until N more events, or until a date. |
A plain resolve regresses on the next event. Resolved in release 1.4.0 regresses when an event comes from 1.4.0 or a
newer release (older instances still running do not reopen it). Resolved in the next release regresses on the first
event from a release created after you resolved it. An ignore with a count or a date reopens the issue as unresolved
when it is reached. Every change names the version it read; if someone else changed the issue first, you are told to
reload.
Merging and splitting
Merge moves other issues of the project into this one: their counts, events and users, and later events with their cause land here too (a fingerprint rule is added in Settings). Split on a merged issue gives it back its own fingerprint and its own count; history that moved stays where it moved.
Create Tasks issue
Files the error into Venom Tasks in the first team (pass a team over the API), with the title, the counts, the release, the flags served, the stack and a link back. The Tasks key is stored on the issue, and the button becomes a link. It needs the Tasks add-on.
Source maps
Upload each generated file's map from CI, per release. They are applied when a stack is read, so you can upload after an error arrived.
curl -X POST "$ORIGIN/incidents/api/v1/releases/$GIT_SHA/artifacts?project=default&name=~/static/app.js" \
-H "Authorization: Bearer $VENOM_API_KEY" --data-binary @dist/app.js.mapname is the generated file's path (~ stands for any host); a bare file name also matches. A request body is at most
4 MB, so gzip bigger maps and send Content-Encoding: gzip (30 MB uncompressed). Sending the same name again replaces
the map. The bytes are kept as a release-owned file next to the uploads of Notes and are never visible in a vault.
Fingerprint rules and releases
Settings lists the project's fingerprint rules (match on exception type, message, module or tag, and set the
fingerprint; merges add one) and its releases. Rules need an owner or admin. Releases come from the SDK's
init({ release }), from CI (POST /incidents/api/v1/releases) and from a successful GitHub deployment_status event
that Venom Tasks' GitHub connection receives, which names a commit.
Roles
Owners and admins can do everything. Developers triage (resolve, ignore, assign, merge, file Tasks issues). Billing members and viewers read. An agent or key acts with the permissions of the member behind it, and every change is recorded with its name and how it was made (app, API or MCP).