Checkmate
Checkmate monitors uptime and server hardware. Point its webhook notification at InfraInbox to get its monitors as incidents, on the destinations you choose, with routing, quiet hours and re-notify on top.
Tested with: built from Checkmate 3.12’s webhook provider; not yet run against a live Checkmate.
What you get
Section titled “What you get”| Checkmate sends | In InfraInbox |
|---|---|
| Monitor down | An incident at Checkmate’s severity, keyed by the monitor |
| Monitor up | The same incident resolves |
| Threshold breach, then resolved | A separate incident for that monitor’s thresholds, opened and resolved the same way |
| Container check failed, then recovered | The same, for container checks |
| Its test notification | A test: the source shows Reachable, no incident |
The built-in rule keeps these incidents open until Checkmate reports the recovery, so none closes just because a day went by.
Prerequisites
Section titled “Prerequisites”- A Checkmate instance that can reach your InfraInbox server.
-
Go to Add source → Checkmate and name it. InfraInbox issues a key for the URL, shown once, with the webhook URL filled in.
-
In Checkmate, open Notifications and create a Webhook notification with the URL:
https://infrainbox.example.com/hooks/checkmate/iik_src_… -
Send its test. The source shows Reachable.
-
Attach the notification to your monitors.
The URL, with a placeholder where the key goes, stays on the source’s Connect tab.
Check it works
Section titled “Check it works”Pause a monitored service. When Checkmate marks it down, an incident opens; start the service again and it resolves.
Limitations
Section titled “Limitations”- Routing rules — send specific monitors to specific destinations
- Built-in rules — edit or override the default rule