Uptime monitoring

[AndrewKvalheim]

Subjects:

• HTTP:
  • [x] SeaGL website
  • [x] GitHub Pages HTTP→HTTPS redirect (#243)
  • [x] OSEM
  • [x] Matrix alias proxy
  • [ ] IRC web client
  • [x] Vaultwarden
  • [x] Mailu web interface
  • [x] Pretalx
  • [x] Nextcloud
• Mail:
  • [x] SMTP
  • [x] IMAP
• Matrix bots:
  • [ ] Patch
  • [ ] Mjolnir
  • [ ] maubot rss
  • [ ] DMARC notifier
• Scheduled tasks:
  • [ ] backups

Possible solutions:

• Ask OSU OSL to monitor each subject.
• Run something like Uptime Kuma and ask OSU OSL to monitor just that.

[strugee]

HTTP

Any particular reason you're thinking to do this ourselves? Is it just agility to not have to wait for OSUOSL to configure stuff?

I was kind of wondering if we could avoid Uptime Kuma and its security issues entirely by having the Matrix bots POST to Nagios on a regular basis or something. (I haven't looked into whether that's possible or easy.)

backups

BorgBase can email us if we're missing backup runs.

[AndrewKvalheim]

SeaGL currently has no monitoring and is hurting for it, and running something like Uptime Kuma looks like an easy improvement. No objections to other solutions, just offering one that’s ready to go now.

[strugee]

https://matrix.to/#/!GkthNMOKdgiNHAErwB:seattlematrix.org/$LjdejvVIOv-rMoOwht4jwa5rZf58tOYtCdgeGuqp6-M?via=seattlematrix.org&via=matrix.org&via=beeper.com some discussion in Matrix about this. See https://github.com/OpenVoiceOS/status

[altsalt]

What is blocking https://github.com/SeaGL/seagl-ansible/pull/29 ?