Every part of errorgap writes into the same place. Start anywhere — errors, servers, uptime, alerts — and the signals meet on one incident with a likely cause.
Error spikes, failed checks, latency anomalies and host findings become one incident with a ranked likely cause and a written summary.
/product/incident-intelligence →Grouping you can readFingerprint grouping, faceted search, the occurrence context viewer, and “Explain this error” on any group.
/product/backtrace →Per-transaction timingPer-transaction timing, web vitals, query attribution, and browser-to-server trace links.
/product/apm →Stream · list · aggregateLive stream, list and aggregate views from the errorgap-agent, tagged by environment and exportable.
/product/logs →Typed event timelinesTyped event timelines rather than video, attached to error groups and incident evidence.
/product/session-replay →Sign-ins, hardening findings, vulnerable packages, open ports and watched-file changes, each with the fix for your OS.
/product/security →Hosts · containers · liveNEWCPU, memory, disk, Docker containers, network and volumes per host, every 15 seconds.
/product/infrastructure →HTTP · TCP · ping, 10sHTTP(S), TCP and ping checks every 10 seconds, with recovery alerts and a 90-day timeline.
/product/uptime →Backtest before you pageNEWRules you backtest against last week, delivered by email, Slack, webhook or the in-app inbox.
/product/alerts →An MCP server with scoped tokens, exposure controls and redaction before anything leaves.
/product/agent-access →GitHub · GitLab · Slack · JiraGitHub, GitLab, Jira, Slack and webhooks, with org-level GitHub and GitLab connections.
/product/integrations →Correlation is the reason the hub is more than a link list. Each capability sends a different kind of signal; the incident engine reads them together on a 60-second cycle.
What an incident carries by the time you open it. Nothing here was assembled by hand.