gorkem-bwl
705c19f7c8
Deployments with restricted egress could not run checks at all: got does not read HTTP_PROXY/HTTPS_PROXY (unlike curl or axios), and NODE_USE_ENV_PROXY only affects Node's built-in fetch, which got does not use. Even a correctly built proxy agent was discarded, because HttpProvider overwrote options.agent on every request. Proxy selection is resolved per check and applied where the agent is chosen. NO_PROXY handling is delegated to proxy-from-env rather than reimplemented, so wildcards, host lists and port-qualified entries behave exactly as operators expect from curl. Infrastructure monitors are excluded by default. Hardware and pagespeed checks both delegate to HttpProvider, so a naive global proxy would also capture Capture agents — which normally sit on the internal network, where proxying them fails or hairpins. PROXY_MONITOR_TYPES is the escape hatch for deployments whose agents genuinely are behind the proxy, and accepts "none" to disable proxying without unsetting the environment variables. Values that are not real monitor types, or that open raw sockets and cannot be proxied (ping, port, docker, grpc, websocket, dns, game), are dropped and logged so a typo cannot silently disable proxying. Agents are cached by proxy URL and TLS mode. Keying on TLS matters: sharing one agent between a strict monitor and an ignoreTlsErrors monitor would leak the relaxed setting across monitors. Caching also preserves pooling, so 50 monitors share tunnels instead of dialling the proxy per check. Both new dependencies were already present transitively (76K total). Notification providers still call out directly and are unaffected; that is a known follow-up for the same class of deployment.
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)