TSYS Group » Chief Operations Officer » Known Element Enterprises - Technology & Facility Services

Parent: #314 (Alerts and delivery thereof)¶

Expand Uptime Kuma monitoring to cover ALL infrastructure:

Scope¶

• HTTPS monitoring for all PFV/SITER hosts (web UIs, APIs)
• DNS monitoring (query checks against netinfra-01/02)
• Database monitoring (MySQL/MariaDB on relevant hosts)
• Docker monitoring (daemon health on container hosts)
• Kubernetes monitoring (API server, etcd — once k8s is online)
• Cloudron service monitoring (all hosted apps)
• Service-specific monitors (LibreNMS, Smokeping, NetDisco, Oxidized, UNPoller, phpIPAM, Uptime Kuma itself, Grafana, Prometheus)

Related¶

• #426 (Uptime Kuma API access — needed for bulk monitor creation)
• #343 (monitoring coverage matrix — validate no overlap with LibreNMS/Beszel)
• #338 (alert transports — Pushover delivery for Uptime Kuma alerts)

Notes¶

• Uptime Kuma is already using Pushover for alert delivery
• This ticket defines WHAT to monitor; #426 defines HOW (API access)
• Consider: Uptime Kuma for HTTP/HTTPS/service availability, Beszel for host metrics, LibreNMS for SNMP/network. No overlap.