HTTP endpoint prober.
Dead simple.
Configure the endpoints you care about, set an interval, and get a Telegram message the moment something goes down — and another when it recovers. No agents, no dashboards, no YAML sprawl.
Everything you need. Nothing you don't.
One binary, one config file. Every probe runs in its own goroutine — no probe blocks another.
Fully parallel
Each probe runs in its own goroutine with its own ticker. A slow or hanging endpoint never delays the others.
Alert on transition only
You get one message when something breaks and one when it recovers. No repeated noise for sustained failures.
YAML config
Method, URL, interval, headers, Basic Auth, and expected status — all per probe, all in one readable file.
Telegram receiver
Plug in a bot token and chat ID and you're done. The notifier interface makes it easy to add more receivers later.
Follows redirects
The HTTP client follows up to 10 redirects automatically. What you configure is the final resolved status code.
Tiny static binary
6 MB stripped, built on scratch. Runs on any Linux host or in a minimal Docker container with no runtime deps.
One loop per probe. Four packages.
Each probe goroutine is independent. State transitions (up→down, down→up) are detected locally and fan out to all configured receivers.
Running in under a minute.
Pull the image or build from source — then point it at your config.