Vigil

Vigil is an open-source status page and infrastructure monitor written in Rust. It pairs scheduled endpoint polling with push telemetry from application workers, tracking services across private networks and public hosts. A single plain-text configuration file drives probes, replica health state machines, and notification dispatch.

Why Vigil instead of Pingdom

Pingdom monitors web applications by executing synthetic probes from global testing stations across multiple continents, offering transaction checks and real user metrics. Vigil evaluates infrastructure health and microservices availability from an operational vantage point you manage yourself. It executes scheduled HTTP, TCP, SSH, and ICMP checks, ingests metrics from application reporters, and presents a public status board. It does not provide global multi-region vantage points or scripted browser user journeys.

The cost difference surfaces as architectures scale. Pingdom prices per check and per user seat, turning dozens of microservice endpoints into large monthly bills. Vigil incurs zero check or seat fees whether you monitor ten endpoints or hundreds of backend replicas and queues. That economic relief shifts operational responsibility to your team: you must maintain the monitoring server, ensure network routes reach inspected nodes, and configure redundant instances if you require external validation.

What it does well

• Dual polling and push telemetry: Combines HTTP, TCP, SSH, and ICMP network checks with application reporters in Node.js, Go, Rust, and Python that transmit host CPU and memory load.
• Multi-replica degradation tracking: Categorizes nodes into healthy, sick, and dead states, using threshold settings like min_replicas_available so a failing replica flags degraded performance before triggering a full outage alert.
• Native queue monitoring: Connects to RabbitMQ management endpoints to detect blocked message consumers before queues stall downstream tasks.
• Minimal operational footprint: Compiles into a single binary running entirely in memory from vigil.cfg, removing external database requirements like PostgreSQL or Redis.
• Multi-channel escalation dispatch: Routes alerts to Slack, Telegram, Matrix, Zulip, Webhooks, and Twilio SMS, supporting backoff intervals and progressive recipient escalation.