v0.9.0: Checks from two places
An alert fires only when two probes agree, which ends the false alarms from a flaky home line. Since this release, interval counts seconds.
v0.9.1: One probe cannot agree with itselfv0.8.2: Webhook tokens stay out of the logv0.8.0: Maintenance windowsv0.7.0: Every check has a namev0.6.0: A status page of its ownChecks can now run from two places at once, and an alert only fires when both see the outage. That ends the false alarms from a flaky home connection, which were most of our bug reports this year. The one breaking change is interval, which counts seconds now instead of minutes. Pegel refuses to start with an old config and says which line to fix.
interval counts seconds, not minutes. Multiply every interval in pegel.toml by 60 before you upgrade, or Pegel will not start.Added
[[probe]]inpegel.tomland the commandpegel probe, which runs your checks on a second machine and reports to your Pegel.agreeunder[defaults]or per check: how many probes must see an outage before an alert fires. It defaults to 2 with two probes or more.- The status page shows which probe saw what.
- Intervals below one minute, down to 10 seconds.
Changed
- Breaking:
intervalis in seconds.interval = 1meant one minute and now means one second, which Pegel refuses. pegel checknames the probes each check ran from.
Removed
- The environment variable
PEGEL_CONFIG, deprecated since 0.7.0. Use--config.
Fixed
- A check that failed and recovered within one interval sent "recovered" without a "down" before it.
Upgrading from 0.8.x
The probe on the second machine gets its checks from your Pegel and needs no config of its own, only the name and a token.
[defaults]
-interval = 1
+interval = 60
+agree = 2
+
+[[probe]]
+name = "home"
+
+[[probe]]
+name = "vps"
Why two probes, and what a year of false alarms looked like: Why an alert needs two probes.
subscribe
New entries and the next chapter by mail, nothing else.