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.

Checks 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]] in pegel.toml and the command pegel probe, which runs your checks on a second machine and reports to your Pegel.
  • agree under [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: interval is in seconds. interval = 1 meant one minute and now means one second, which Pegel refuses.
  • pegel check names 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"
A terminal: pegel check refuses interval = 1 on line 2 of pegel.toml and suggests 60. After a sed command it reports shop and docs as ok from home and vps.
The check before the upgrade, on our own config.

Why two probes, and what a year of false alarms looked like: Why an alert needs two probes.

Comments

Buy Logbuch