The OpenAPI spec only listed `limit` for GET /monitors/team/with-checks, but the route's Zod schema (getMonitorsWithChecksQueryValidation) also accepts page, rowsPerPage, filter, field, order, type, and explain. Users hitting the endpoint via Swagger UI would either get rejected with "page is not allowed" (when guessing param names) or miss pagination entirely. Adds the missing parameters with constraints mirrored from the validation schema. Also bumps `limit` max from 50 to 100 to match the schema (was 100 in code, 50 in spec). Closes #3354
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.
Related repositories
- Capture Agent (Optional, provides additional server insights)