We currently send emails from the Prometheus AlertManager which is great as long as those emails are read by the right person in a timely manner. There are some issues though:
mail may be send with unencrypted transport (containing sensitive log information)
difficult to update list of recipients
no easy place to see history of alerts
if the mail server is down, you get no alerts
Some effort has recently been made to start using Matrix inside Tor, and this seems like an oppportunity to move with that momentum and solve some or all of the above issues.
If desirable, I could write an Ansible role to run this as a systemd user service on a TPA machine as we have done for Metrics services in the past, or you could write some Puppet to do the same.
Designs
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
just to throw this out there somewhere, there's many more possible ways of doing notifications, so we might consider some sort of unified bridge.
one that came up recently on Hacker News is https://ntfy.sh/, which is basically like a patch panel for notification hooks.
but there's tons more implementations of this, from all over the stack, it's quite confusing. let me just throw them all out here and i'll sort through this at some future time:
apprise: "Push Notifications that work with just about every platform", IRC support through https://n.tkte.ch/, matrix, sms, signal, email, desktop, etc, missing mastodon
i just found out there's a maubot plugin called alertbot which bridges alertmanager and matrix. we could clearly use this to send notifications and, rather neatly i think, also do other notifications like GitLab web hooks and other nifty things...
@ahf anyone you know considered running a maubot for tor?
For my home setup, I have pondered having a signald with a group in it for alertmanager alerts - that may be worth considering as well. It's written by one of the old IRC hax0rs. See: https://github.com/dgl/alertmanager-webhook-signald
configuration is okay, and i managed to authentify with nickserv (but it doesn't do registration on its own, i don't think). it also doesn't support SASL auth but there is a patch for it.
but the output is just awful, as it dumped a bunch of JSON in my channel instead of formatting it correctly, still doing some tests.
another webhook/irc endpoint is this thing called bot (ugh) which seems to have some interactivity as well, which is interesting. it seems it pages users on rotation, with private messages. not clear if it supports authenticating with the IRC server (which is definitely a problem). documentation poor. not in debian and not tested.
looking at this again because we're having trouble with the IRC relay. i've also found that upstream prometheus docs refer to another project which is not linked here (go-neb)...