Features · Alerting & Incidents · Incident Management
Alerting & Incidents · Incident Management

Auto-created from an alert.
Logs from 5 min before attached.

An alert fires; an incident opens; the logs from the 5 minutes before the fire are automatically attached. Timeline, ownership, status, comms — all in one place, all linked, all auditable.

INC-2841 · checkout 5xx
14:31 alert fired · severity page
14:31 incident opened automatically
14:31 logs 14:26–14:31 attached
14:34 acknowledged · sascha
14:52 resolved · 21 min
— Why this matters

The logs you need are the ones from before it broke.

01

By the time you SSH in, the evidence has rotated.

The agent detects the crash and collects the five minutes before it, plus two minutes after. You read the cause, not the aftermath.

02

An incident should assemble itself.

Alert fires, incident opens, logs attach, metrics snapshot at crash time. Nobody types any of that during an outage.

03

Blast radius is a graph question.

The dependency map shows what else sits behind the thing that failed, which is the part people underestimate.

— What's included

What lands in an incident.

Crash detection
MySQL, PostgreSQL, Nginx, Apache, Redis and Caddy, watched by the agent.
Logs from before and after
Five minutes prior, two minutes following, from the service files, syslog and dmesg.
Filtered dmesg
OOM kills, killed processes and segfaults picked out of the noise.
Metrics at crash time
CPU, memory and load as they were, not as they are now.
Status workflow
Investigating, identified, monitoring, resolved — four states, because five would be lying.
Impact graph
Dependency-based, so the question "what else is affected" has a picture.
Comments
On the incident itself, where the timeline is.
CSV export
For the review that happens in a spreadsheet.
— How it works

The incident assembles itself.

1

Detect the crash

Service and host state changes open an incident without anyone filing it.

2

Collect the evidence

Logs from before and after, filtered dmesg and the metrics at crash time are attached while they still exist.

3

Work it, and see the reach

Status workflow, comments and an impact graph of what depends on the thing that broke.

— Works with

Connected capabilities

— FAQ

Questions, answered honestly.

How long are pre-fire logs kept? +
5 min by default, 15 min on Pro, 30 min on Enterprise — held in a rolling buffer on the agent.
Can I open an incident manually? +
Yes — "open incident" button, attach hosts + tags, severity. Same UI as auto-opened ones.
Is there an export? +
JSON + PDF + signed timeline export. Useful for SOC 2 evidence.

The first 5 minutes, captured automatically.

Incident management from Starter; Slack auto-channel from Pro.

Get early access Back to Alerting & Incidents