Files
Checkmate/server
gorkem-bwl 2055943876 fix: make dateRange optional for hardware details endpoint
The Joi validation marks dateRange as optional, but the controller was using
requireString() which throws a 400 error when dateRange is missing.

Changed to optionalString() with "recent" as the default value, matching
the behavior of other similar endpoints and the Joi validation schema.
2026-01-16 13:11:41 -05:00
..
2025-06-01 11:55:16 -07:00
2026-01-14 19:28:17 +00:00
2026-01-15 21:05:00 +00: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
2025-07-21 10:34:04 -07:00
2025-04-20 11:29:53 -07:00
2026-01-14 19:28:17 +00:00
2025-04-20 11:29:53 -07:00
2026-01-09 13:36:58 -08:00
2025-08-11 13:55:01 -07:00
2026-01-14 19:28:17 +00:00
2026-01-14 19:28:17 +00:00
2025-06-01 11:55:16 -07:00
2026-01-14 19:28:17 +00:00
2026-01-14 19:28:17 +00: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.