gorkem-bwl
a23e4de1d3
## Changes - Remove location field from CheckMetadata, MonitorStatusResponse, Check model metadata schema, and location index - Remove location from checkService.buildCheck() and MongoChecksRepository toDocument/mapMetadata - Rewrite SuperSimpleQueueHelper Step 2b: instead of creating separate Check documents per Globalping location, backfill locationResults into the same Check document after the local check is buffered - Rewrite findLocationChecksByMonitorId to use $unwind on locationResults subdocument array instead of querying by metadata.location - Remove metadata.location filter from findUptimeDateRangeChecks - Pass locationResults through in toEntity ## Benefits Single Check document per monitoring cycle now contains both local results (top-level fields) and per-location Globalping results (locationResults array). This eliminates document proliferation and simplifies queries.
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)