Statping-ng

Statping‑ng is a self‑hosted status page and uptime monitoring platform written in Go. It exposes a RESTful API for managing services, checks, and notifications while rendering a modern, responsive web UI built with SASS‑based styling. The core of the application is a lightweight scheduler that periodically probes HTTP, TCP, UDP, ICMP, and gRPC endpoints and records metrics in a relational database. This makes Statping‑ng suitable for both small personal projects and enterprise‑grade monitoring of complex microservice ecosystems.

Key Features

• Multi‑protocol support – probes HTTP, TCP, UDP, ICMP and gRPC services with configurable intervals.
• Rich notification stack – built‑in integrations for Slack, Discord, Telegram, Email (SMTP), Webhooks, and a generic “mobile” notifier via push services.
• RESTful API – CRUD endpoints for services, groups, and notification rules; authentication via JWT or basic auth.
• Custom styling – SASS‑powered theme system that lets developers override the default UI or embed a branded status page into existing sites.
• Service grouping – logical categorization of checks, enabling dashboards per team or product line.

Technical Stack

Core Capabilities

• Health checks – configurable timeouts, retries, and success criteria (status code ranges or response body regex).
• Metrics – uptime percentage, response latency, and status history exposed via /api/v1/stats.
• Webhook API – external systems can push custom events to trigger status updates or notifications.
• OAuth2 & LDAP – optional integration for corporate environments (configurable via env vars or config file).
• Plugin hooks – developers can inject custom logic by implementing a Go interface that runs before/after checks.

Deployment & Infrastructure

Statping‑ng is designed for zero‑downtime self‑hosting. A single binary runs on any OS with Go runtime support, and the Docker image supports Docker Compose or Kubernetes via Helm charts (community‑maintained). Horizontal scaling is straightforward: multiple instances can share a single database and use a load balancer; the scheduler state is persisted in DB, so only one instance should perform checks to avoid duplicate probes. For high‑availability, a Redis or Etcd lock can be added to coordinate check execution across pods.

Integration & Extensibility

• Webhooks – any service can post to /api/v1/webhook to trigger a status change or log an event.
• Custom notifiers – the notifier framework is pluggable; developers can write a Go module that implements the Notifier interface and add it via configuration.
• SASS themes – modify _variables.scss to align the status page with corporate branding; the build process compiles on startup.
• CLI hooks – pre‑deploy scripts can run statping migrate and seed initial services.

Developer Experience

• Configuration – YAML/JSON files or environment variables; the README and Wiki contain detailed sections for Linux, Windows, Mac, and Docker.
• Documentation – comprehensive API docs are auto‑generated from OpenAPI specs; the GitHub Wiki hosts guides for custom notifiers, deployment patterns, and troubleshooting.
• Community – active GitHub discussions, a Slack channel, and frequent releases (stable, unstable, dev branches) keep the codebase modern.
• Licensing – permissive MIT license allows commercial use without copyleft obligations.

Use Cases

Advantages Over Alternatives

• Performance – Go’s concurrency model yields low CPU/memory overhead even with hundreds of checks.
• Simplicity – No heavy JS frameworks; a single binary plus optional Docker image reduces attack surface.
• Flexibility – Full control over database choice, notifier stack, and UI theme; no vendor lock‑in.
• Licensing – MIT license allows unrestricted commercial deployment, unlike some SaaS‑centric open‑source projects.
• Community & Maintenance – Actively maintained fork with