I had to do this again today for team#41667 and it was really
useful to have this around. I also noticed I was missing the `amtool`
invocation, even from the other ticket, so it was kind of important to
add this to the wiki immediately after all.

Alertmanager is now publishing alerts to the newly-registerd #tor-alerts
channel.

We've decided to change the channel name since the new monitoring system
is not related to nagios anymore. We prefer having a more generic name.

See team#41631

The linter I use locally (markdownlint) is set to be very strict and
there are many other issues that I didn't fix. The other issues are
almost all about lines being too short or bullet lists being indented by
one space. I just wanted to fix the easiest details that surely won't
have an impact on the content.

the output of `trocla --help` is really not helpful. With the README
file at least we can see what other subcommands exist and how they're
used.

There was a URL defined for "Trocla" but it wasn't used, so I just
linked it up on the first appearance of the software name.

service/ci: expand on workaround for team#41621

See merge request !50

Normal chunks are okay to backup without any special snapshotting, but
WAL files are written on the fly by Prometheus, and doing a backup
with Bacula will lead to inconsistencies in the storage which can make
recovery more difficult. See also https://github.com/prometheus/prometheus/pull/14317

this should make it easier to jump to the section we want to see.

The anchor has changed, probably because the section was renamed

We seem to be converging over something that covers both flow and
architecture, but even including other mail hosts. It's pretty neat!

See team#41009

Now we have two models: one of email delivery flow, the other of the
redundancy architecture.

Turns out the latter might be clear enough on its own; the main
difference is it omits other mail host snowflakes like lists and the
other mail hosts (gitlab, rt, etc).

See team#41009

This is better, but still hard to read, I'm starting to think I just
need to split this in two diagrams: one to display redundancy and
location, the other for message flow.

This really tells me our naming convention sucks and we should have
picked example0 instead of example-01... But anyway.

This is clunky and overcrowded, but a necessary step to realize we
just can't draw all the lines.

this clarifies the diagram a little bit and starts working on the
clustering design.

This struck me while doing star training with @lelutin: we *do* run
the NRPE checks by hand quite often, and especially
dsa-check-packages. We need to port this to something else eventually.

See: team#40755