From SDK to incident, automatically.
Install the SDK and ship. Errorgap captures and groups errors, correlates them with uptime, latency, and deploy signals, then assembles the evidence into an incident you can investigate.
Drop in the SDK
One package per runtime. Initialize with your project key and the SDK starts capturing — no manual try/catch plumbing required.
We catch, group, dedupe
Exceptions are fingerprinted by stack signature and message — thousands of occurrences of one bug collapse into a single group with a count and a graph.
Signals become an incident
A heuristic engine promotes elevated error rates, uptime failures, latency spikes, and deploy correlations into a first-class Incident.
Likely cause, in one place
A deterministic likely-cause panel, a confidence score, an evidence timeline, and a written AI summary — everything to act, without tab-hopping.
When signals become an incident.
Errorgap's heuristic engine watches for six trigger conditions and assembles the evidence into one Incident object — instead of leaving it scattered across separate views.
One object. All the evidence.
High-volume error groups, uptime failures, error-rate spikes, latency anomalies, infrastructure saturation, and deploy correlations — when a condition fires, it becomes a first-class incident with a full evidence trail.
- Six heuristics, evaluated on a 60-second cycle
- Evidence timeline: error groups, releases, uptime checks, APM traces
- Open → Acknowledged → Resolved lifecycle
- Manual incidents for what the heuristics don't catch
From signals to a likely cause, automatically.
The deterministic correlation panel runs the moment evidence loads. It derives a likely cause, scores confidence and shows the signals behind it. On plans with AI, a written summary follows on top of that evidence.
A confidence score, then a plain-English read.
Summaries write themselves when an incident opens or grows. Summarize again is still one click. The AI explains the evidence; it doesn’t decide the cause.
- Confidence scored 10–90% from backtrace overlap, similar incidents and timing.
- A summary, likely cause and next steps written when the incident opens.
- “Explain this error” on any error group, with who hits it and on which page.
- Similar incidents found by meaning, not just stack match.
Runs on an errorgap-run model. Prompts are redacted first.
- Roll back to v2.14.0 or guard the token read.
- Check the 18 customers who retried during the window.
Every signal, framed in context.
errorgap connects the exception to the line, the line to the deploy, and the deploy to the person who can fix it, then watches availability, latency and the hosts underneath.
The line. The frame. The fix.
Every captured exception lands you on the offending source line with context and the full call stack. Same-signature errors collapse into one group; faceted search narrows thousands of groups by release, browser or user.
- Source-map upload, including index maps
- Occurrence context viewer and Aggregates tab
- Fingerprint grouping, merge/split, regression detection
Watch your production breathe.
Stream errors, warnings and structured logs straight from your runtime. Filter by level, source, release or environment, then export what you found.
- Live stream, sub-second latency
- Environment tags: production, staging, dev
- CSV and NDJSON export
Know when your users can't reach you.
HTTP, TCP and ping checks sweep every 10 seconds. Failures open incidents automatically and recoveries send their own alert.
- HTTP / TCP / ping · SSL expiry
- Recovery alerts, not just failures
- Compare with the previous period
Slow routes surface before users file tickets.
Transaction timing from every request and job, plus web vitals from the browser. Transaction IDs link each error to the request it happened in.
- Browser performance: LCP, INP, CLS
- Browser-to-server trace links
- Query attribution per transaction
Hosts, containers, network and volumes, live.
CPU, memory and disk per host every 15 seconds, plus Docker containers, interface throughput and mount options. One host can feed several projects.
- Host pressure shows up as incident evidence
- See Infrastructure →
Rules you can test before they page you.
Backtest a rule against last week before you turn it on. Deliver by email, Slack or the in-app inbox, with a daily digest for the rest.
- Per-person notification preferences
- See Alerts →
Tie every error to a release.
Deploy markers on every chart, with error counts relative to the release before. Upload source maps per release so frames read as your code.
- Relative counts per deploy
- Deploy correlation as an incident heuristic
Know who got in, and what’s open.
The same agent that ships your logs and metrics reads sign-ins, SSH and sudo config, packages and open ports, and turns them into findings with the fix command for your OS.
Sign-ins
SSH and web sign-ins, new locations, odd hours, shared accounts.
Hardening
Root login, password auth, keys, sudo paths to root.
Vulnerabilities
Installed packages matched against OSV; OS end-of-life.
Exposure
Listening ports, what’s behind them, firewall state.
Changes
Watched files (sshd_config, sudoers, authorized_keys) diffed.
Malware
Optional scheduled ClamAV scans, low priority, results as findings.
Give your AI agents production context.
Errorgap exposes a Model Context Protocol server so Claude, Cursor, Copilot, and any MCP-compatible agent can query live production data — error groups, incidents, backtraces, uptime status, and proposed fixes — without exposing your browser session.
{
"mcpServers": {
"errorgap": {
"url": "https://app.errorgap.com/mcp",
"headers": {
"Authorization": "Bearer egmcp_…"
},
"scopes": ["errors:read", "logs:read", "source:read"]
}
}
}
Scoped, redacted, per project.
- Tools: search and read errors and backtraces, list and read incidents, explain an incident, find its likely cause, propose a fix, read deploys
- Per-project exposure toggles — six categories of data
- Org-level defaults with per-project overrides
- Regex-based redaction rules with live preview
- Scoped API keys, revocable from the Agent Access page
Three lines and you're shipping.
Pick your runtime. The SDK does the rest — async-safe, fork-safe, and zero overhead in dev.
Wired into the tools you already use.
Errorgap doesn't try to replace your issue tracker or your chat. It connects to them and stays out of the way.
Per-event pricing. No seat tax.
Pay for what you capture, not who's logged in. Every plan includes every feature except the bits genuinely tied to enterprise compliance.
- 7-day retention
- 1 project
- 200 replays · 1 uptime monitor
- Email alerts
- Infrastructure & Security agent
- AI summaries & explanations
- SSO
- Audit log
- 30-day retention
- Unlimited projects
- 5k replays · 10 uptime monitors
- Slack + GitHub
- AI summaries & explanations · 50/day
- Infrastructure & Security agent
- SSO
- Audit log
- 90-day retention
- 25k replays · 50 uptime monitors
- SSO · SAML
- Audit log
- AI summaries & explanations · 200/day
- Infrastructure & Security agent
- Priority support · 4h SLA
- Unlimited AI
- Infrastructure & Security agent
- Dedicated infrastructure
- Custom data residency
- Custom SLA
- Security review
- Solutions architect