Checkmate opens an incident on the first failed check, closes it on recovery and keeps the history. What broke, when, for how long and who resolved it: answered from a dashboard instead of a spreadsheet.
The first failed check opens an incident and fires alerts on the monitor's channels. When a check passes again, the incident resolves automatically and a recovery notification follows, so the timeline writes itself while you work the problem.
Start time, end time and duration come from the checks, not from whoever remembered to update a ticket at 3am.
Fixed the problem out of band and don't want to wait for the next scheduled check? Resolve the incident manually from the incidents page, with an optional comment on what you did.
The resolution records who closed it and what they wrote. 6 months later, when the same alert fires, the comment from last time is the head start.
Filter incidents by monitor, date range and status, with durations and an average resolution time computed for you. That is the raw material for SLA reporting and the fastest way to spot patterns.
Incidents that land at the same hour usually trace to a cron job. Durations that keep growing point at a slowing recovery process rather than new failures. The history is where those patterns become visible.
No dedicated incident commander, no war room. The incident record assembles itself from the checks, which is the only process a 3-person team will consistently follow.
Agencies and MSPs with uptime commitments need defensible numbers. Incident durations and resolution times come straight from check data, on your own servers.
The timeline answers when it started, when it ended and how long it took before the meeting starts, and the resolution comment holds the one-line summary of the fix.
An incident is the stretch between the first failed check and the recovery, one record per outage rather than a pile of alerts. Active incidents show elapsed time as they run.
Every incident closes as automatic or manual, and the label is stored. You can see at a glance how much of your recovery is self-healing and how much needed hands.
Manual resolutions store the resolving user and the comment they left. The audit trail exists without anyone maintaining it, which is how audit trails survive.
Average resolution time is computed across whatever filter you are looking at, per monitor, per month or fleet-wide. The number your SLA conversation starts from.
Automatically. The first failed check on a monitor opens an incident and fires alerts, and the incident stays active until a check passes again or someone resolves it manually. No manual declaration step.
Yes. The incidents page offers a manual resolve on every active incident, with an optional comment. The incident records the resolver and the comment, labelled as a manual resolution.
Yes. Every incident keeps its start time, end time, duration, resolution type and, for manual closes, who resolved it and their comment. The history is filterable by monitor, date range and status.
That is what it is for. Durations and average resolution time are computed from check data on your own instance, so the numbers behind an SLA report are yours to verify and export.
Through its notification channels, yes: PagerDuty is a native channel, alongside Slack, email and 9 others. Escalation policies and rotations stay in your paging tool, Checkmate feeds it.
No. Like everything in Checkmate it ships in the open-source core under AGPL-3.0, self-hosted on your servers with no tiers to unlock.
Websites and APIs checked from 6 continents.
ICMP reachability for anything with an IP.
Databases, mail and SSH watched at the socket.
Records resolved against the resolver you choose.
Handshake checks for ws:// and wss:// endpoints.
The standard health protocol, checked on schedule.
More than 100 game types over native protocols.
CPU, memory, disk and network via the Capture agent.
Container status, health checks and resource usage.
Lighthouse scores and Core Web Vitals on a schedule.
Certificate expiry caught before browsers complain.
Branded public pages served from your own instance.
12 native channels, from email to PagerDuty.
All featuresCheckmate is open source under AGPL-3.0. Self-host it and this feature ships free, on your servers, with your data.