Automatic Kagi Status Page Updates

happinessattack

Many services have status pages that automatically ping monitored resources to return a simple up/down/degraded result. Kagi should as well.

Although the explanation of downtime events is understandably a manual process, downtime can likely be detected and reported to the customer without human intervention.

Something like Uptime Kuma would be fully sufficient in such cases.

Users should be able to monitor Kagi's uptime and downtime without using the community/Discord.

Database

I use Uptime Kuma so I can vouch that it's a nice piece of software. It does lack the more detailed incident management that status pages are known for though.

I'm sure Kagi has monitoring internally, so maybe they can automatically create incidents in cState (their current status page) off of it, or use solutions like this. Just gotta be sure that an incident is actually an incident and not a hiccup of the monitoring software.

happinessattack

Database As an FYI, from the cState README:

Please note that with all that cState can do, it cannot do automatic monitoring out of the box. [...] You can think of the cState status page as an informational hub. Because the software is static, it cannot directly monitor any services in real time.

Perhaps neither cState nor Uptime Kuma are the right approach. Nonetheless, I am glad this is under consideration. 🙂

Vlad

Thanks for the suggestion we will look into it.

Value7609

With https://cachethq.io you can also add more details to incidents

Gnome and openSUSE are using it, below the links, so you can see how it could look:

https://status.gnome.org
https://status.opensuse.org

Seems to be maintained again https://blog.cachethq.io/cachet-3-x-announcement/ but idk what the current status of it is.

Value7609

happinessattack yes that's why this feedback here exists, as https://status.kagi.com uses cState

Vlad

Yep we would prefer automatic monitoring solution this time.