See prometheus-alerts!21.

I used the following Postgresql query on the RT database to estimate the
number of outgoing mails per month from the service over the last year:

    SELECT COUNT(*), EXTRACT(YEAR FROM created) AS year, EXTRACT(MONTH
    FROM created) AS month FROM transactions WHERE objecttype =
    'RT::Ticket' AND type = 'Correspond' and CREATED >= (current_date +
    '-1 year'::interval) group by month, year order by year, month;

I reviewed the entire page to make sure it flows correctly. I mostly
worked on splitting up the per-service procedures in different
sections instead of one long list, but also reworked the headings to
have better categories that will look better in the TOC.

I also warn about individual reboots because the more common use case
is fleet, or at least cluster-wide reboots.

See: team#33406

See: team#32920

This merges a bunch of different procedures that had accumulated all
over the place.

It also adds new procedures that were flying around as copy-paste
ideas in IRC channels. It should now be possible to copy-paste from
the wiki instead, which is a slight improvement.

See: team#32920

The formatting for these fields matter, especially categories as it
seems it will not render the post unless there's a newline under the
field name.

Encountered in team#40955 and team#40939.

Surprisingly little change... most of the remaining issues are
interoperability issues, or issues that escaped our inspection in
TPA-RFC-15 (e.g. SRS).

That's the part that doesn't change... rendered as HTML, this will
make it italic, like a quotation which should distinguish it from the
changes.

It's actually pretty unlikely we can completely defer mailing list
services to an external service provider. It doesn't hurt to ask,
however, so let's keep it here but mark it optional.