Files
Checkmate/server
gorkem-bwl 943ef92053 fix: rename "breached" status to "exceeded" for clarity
The word "breached" in infrastructure monitoring was confusing users
as it implied a security breach. Renamed to "exceeded" which better
describes threshold violations (e.g. "threshold exceeded").

## Changes
- Renamed monitor status value from "breached" to "exceeded" across
  server types, status service, queue helper, notification builder,
  email subject lines, and MongoDB aggregation queries
- Renamed client types, status box/label components, translation key,
  and infrastructure page props to match
- Added DB migration (0005) to update existing monitors with the old
  status value
2026-03-11 01:31:05 -04:00
..
2025-06-01 11:55:16 -07:00
2026-03-04 17:50:27 +00:00
2026-03-05 19:16:08 +11:00
2025-04-20 11:29:53 -07:00
2026-03-02 21:52:22 +00: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
2025-07-21 10:34:04 -07:00
2026-03-03 18:26:42 +00:00
2026-01-15 22:33:25 +00:00
2025-04-20 11:29:53 -07:00
2026-01-09 13:36:58 -08:00
2026-03-07 01:40:07 +05:30
2025-06-01 11:55:16 -07:00
2026-03-06 14:27:57 -08: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.