v0.9.1: One probe cannot agree with itself
Pegel refuses a config that asks more probes to agree than it has. The release job writes checksums after every build has finished.
v0.9.0: Checks from two placesv0.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 ownpegel check now refuses a config whose agree is larger than the number of probes. In 0.9.0 such a config started without a word and could never alert, because one probe cannot agree with itself. Two people ran into it in the first three days, both on a Raspberry Pi with a single probe.
Fixed
- A config with
agree = 2and one[[probe]]started and never fired an alert.pegel checkandpegel runstop and name the line to fix. - Without any
[[probe]],agreedefaults to 1 again, as the notes of 0.9.0 said. pegel proberetried a refused token every second. It waits 30 seconds between attempts now and logs why.
Changed
- The release job writes
SHA256SUMSafter the last build has finished. Details in the checksum incident.
probes := max(1, len(cfg.Probes))
if cfg.Defaults.Agree > probes {
return fmt.Errorf("%s line %d: agree = %d needs %d probes, found %d",
cfg.Path, cfg.Line("defaults.agree"), cfg.Defaults.Agree, cfg.Defaults.Agree, probes)
}$ pegel check --config pegel.toml
error: pegel.toml line 3: agree = 2 needs 2 probes, found 1
subscribe
New entries and the next chapter by mail, nothing else.