Pegel

What comes after 0.9.0, and the three things we decided not to build

Alert routes, DNS checks and a container image for the probe come next. A plugin system, a hosted Pegel and an app do not.

A timeline of Pegel’s releases in 2026: v0.6.0 on 2026-03-02, v0.7.0 on 2026-05-11, v0.8.0 on 2026-08-24, v0.8.2 on 2026-10-05 and v0.9.0 on 2026-11-09.
Every release of 2026 so far. v0.8.1 is missing because its build failed and it never shipped.

Pegel 0.10.0 gets alert routes, so one check can page one person and mail another, DNS checks next to HTTP and TCP, and an official container image for pegel probe. We aim for 2027-02. So far we have missed every date we gave by about three weeks, so plan for March.

Alert routes

Today every alert goes to every address in [notify]. A [[route]] will match checks by name and send their alerts to their own addresses or webhooks. Half the feature requests this year were a variant of this one.

[[route]]
checks = ["shop", "shop-api"]
mail = ["[email protected]"]

[[route]]
checks = ["docs"]
webhook = "https://hooks.example.com/docs-team"

DNS checks

A check that asks a name server for a record and compares the answer. The false alarm we had in 2026-08 was a slow DNS answer, and a DNS check would have said so directly.

A container image for the probe

pegel probe is one binary and a token. An image saves a step for people who put it on a NAS or a VPS that already runs containers, and most of you do.

What we will not build

A plugin system. Every request for one so far was for a check type, and we would rather add the check type and test it.

A hosted Pegel. Two people with day jobs cannot promise the uptime a hosted monitor needs.

An app. Alerts reach a phone by mail and by webhook, and a webhook reaches any push service you already use.

Comments

Buy Logbuch