Files
Checkmate/server
Craig Lawson ec01a5dfe4 Add egress state and probe service (#3937)
Adds the EgressService that probes a configurable set of reliability targets
(ping, TCP or HTTP) when asked, persists a single instance-wide egress state
document, and runs a recovery poll loop while egress is degraded. Adds the four
egress settings fields with validation. The worker constructs and initialises
the service but nothing calls assessAfterFailure yet, so behaviour is unchanged.

🔧
2026-09-14 10:34:12 +01:00
..
2026-07-09 10:21:09 -07:00
2025-04-20 11:29:53 -07:00
2025-09-22 12:53:44 -07:00
2025-04-20 11:29:53 -07:00
2025-04-20 11:29:53 -07:00
2026-05-29 10:33:15 -07:00
2026-06-09 12:35:57 -07:00
2026-06-09 12:35:57 -07:00
2025-04-20 11:29:53 -07:00
2026-08-25 15:16:54 -07:00
2026-08-25 15:16:12 -07:00
2026-06-09 12:35:57 -07:00

Checkmate backend

The backend service for Checkmate, an open source uptime and infrastructure monitoring application

This directory contains the backend of Checkmate, which handles data processing, storage, and API services for the Checkmate monitoring tool. The backend is responsible for managing uptime checks, handling real-time alerts, and storing historical monitoring data.

Checkmate's backend is designed to be lightweight and scalable, ensuring reliable performance even with a high number of active monitors.

Installation & documentation

For setup instructions, configuration details, and deployment guidelines, please visit our official documentation at docs.checkmate.so.