Uptime Kuma

River Oaks Church - Created May 2025

We use a self-hosted application called Uptime Kuma to host a service that periodically pings certain IPs to check the status of devices at River Oaks.

The url for Uptime kuma (editor) is:

https://status.ro.church/dashboard

The public monitoring url is:

https://status.ro.church/status/network

This service is hosted on Docker running on the Oracle VM in the cloud.

Application readiness monitors

Do not use ICMP alone for a workflow that can answer HTTP. The Portal sermon slides monitor uses HTTP(s) - Keyword against https://portal.ro.church/health/sermon-slides.php every 60 seconds with two retries and a 15-second request timeout. Require the literal keyword "service":"sermon-slides" and accept only 200 through 299. The keyword keeps an authentication or generic error page from becoming a false positive. The endpoint is content-free and returns 503 when the portal's five-minute monitor is stale or a systemic sermon dependency is unavailable. It returns 200 for ready and warning-only degraded states.

The detailed dependency, error code, recovery behavior, maintenance window, and operator commands are documented in Focused portal workflow alerts. Uptime Kuma is the independent availability signal; it does not replace focused alert email, SQL processing history, or the systemd journal.