Error Tracking

Provenance provides built-in error tracking that captures, deduplicates, and groups errors across your applications. Errors are recorded as interactions with automatic fingerprinting, release tracking, and source map resolution.

How It Works

SDKs capture errors — captureException() computes a fingerprint, builds a structured payload, and logs it as an interaction
BFF upserts error issues — when an error interaction arrives, the system creates or updates an error_issue record (grouped by fingerprint + origin)
UI displays issues — the Errors page shows grouped issues with event counts, status, and stack traces

Error Issue Lifecycle

open → resolved (with release)
open → ignored
open → muted
resolved → open (reopen)
resolved → regressed (auto: new error in different release)
regressed → resolved
regressed → open
ignored → open
muted → open

Regression Detection

When an error issue is marked resolved with a specific release, and a new occurrence arrives tagged with a different release, the issue automatically transitions to regressed. This lets you know immediately when a fix didn't hold.

System Entities

Error tracking uses system-defined resource types and actions:

Entity	Mnemonic	Description
Resource Type	`ERROR`	System resource type for all error interactions
Action	`UNHANDLED`	Uncaught exceptions
Action	`REJECTION`	Unhandled promise rejections
Action	`HTTP_ERROR`	HTTP 5xx errors
Action	`CAUGHT`	Manually captured errors

API Endpoints

Method	Endpoint	Description
GET	`/api/error-issues`	List error issues (with filters, sorting, pagination)
GET	`/api/error-issues/:id`	Get issue detail with latest stack trace
GET	`/api/error-issues/:id/events`	List individual error events
PATCH	`/api/error-issues/:id/status`	Update issue status
POST	`/api/origins/:id/releases`	Create a release
GET	`/api/origins/:id/releases`	List releases
POST	`/api/origins/:id/releases/:releaseId/sourcemaps`	Upload source map
POST	`/api/sourcemaps/resolve`	Resolve stack frames

CLI Commands

provenance errors list --origin my-app --status open
provenance errors get <issueId>
provenance errors resolve <issueId> --release 1.2.3
provenance releases create --origin my-app --version 1.2.3
provenance sourcemaps upload --origin my-app --release 1.2.3 ./dist

MCP Tools

Available for AI agents: get_error_issues, get_error_issue, update_error_issue_status, get_releases, create_release.

Overview