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.

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

drop is the target that avoids ICMP responses. I believe this was just
an omission when copy/pasting the command above.

This will make it a little more obvious where to find copies of it if
we change it, and will allow operators to recover from a broken
procedure if it was changed but the copies were not updated by mistake.

Done during @lelutin's onboarding, tpo/tpa/team#41599

We keep rebuilding such a list in many places, in new-person, the
OnBoardingAgendaTemplate... Just make a canonical location.

Done with @lelutin during his onboarding, tpo/tpa/team#41599

Done with @lelutin during his onboarding, tpo/tpa/team#41599

This is less likely to be the "next step" after the OpenPGP setup...

Done with @lelutin during his onboarding, tpo/tpa/team#41599

Done with @lelutin during his onboarding, tpo/tpa/team#41599

Done with @lelutin during his onboarding, tpo/tpa/team#41599

Done with @lelutin during his onboarding, tpo/tpa/team#41599

Done with @lelutin during his onboarding, tpo/tpa/team#41599

Onboarding @lelutin (tpo/tpa/team#41599), I realized I was telling him
"oh just follow the later thing" so that means I need to tweak the
guide.

I don't believe the previous procedure works...

I have given tpo/tpa access to the web group instead.