Self Hosting Log - 006 - Uptime Kuma

Version two of my status page!

You may recall if you’ve been following my posts or just going through my backlog, that I spun up a status page with Statusfy a little while ago. It was a really nice set up and I considered it a log of all my self hosting activities. But I noted that the project didn’t seem to be getting a huge amount of love. While I enjoyed it’s statically generated nature, that meant it required manual updates. Which is fine for posting maintenance activities, but is not fine for reporting on outages since there’s nothing actually polling the services to see if they’re up or not.

The Self Hosting community had some answers already, but I felt they were a bit dated. Then, almost out of no where it seemed, Uptime Kuma entered the scene and I thought this could be a replacement for me! While it did provide internal monitoring initially, it didn’t have the same status page option as Statusfy. Thankfully, open source software is amazing and sure enough, a status page came rolling down the pipe soon enough. You can take a look at my Compose file below.

version: '3.3'

services:
  uptime-kuma:
    image: louislam/uptime-kuma
    container_name: uptime-kuma
    volumes:
      - /srv/uptime-kuma:/app/data
    ports:
      - 3001:3001
    restart: unless-stopped

You may notice the port mapping in Compose, but when you actually visit the status page you’re visiting it over 443. That’s because I’ve this running on AWS with an Application Load Balancer in front of the EC2 instance. I set it up like this since I figured I should make it as available as possible. However that posed its own challenges since there isn’t really a documented approach to making the service highly available. Plus as you may have seen in a previous post, I’ve already experienced downtime with my status page which has been unfortunate. I don’t really blame the tool for this, I was running it on a T4G.Nano so with only 512MB of RAM available to the instance and with the OS grabbing some for itself, it was probably struggling. I’ve since moved to a T4G.Micro and have been monitoring it (ironically, lol), so far it’s been going okay so if it stays like this for two or so weeks, I’ll consider it solved.

Hopefully, you’ll see this status page start to grow over time with more services being added to it. I also want to implement its Push monitor category, as some of my local infrastructure isn’t actually being monitored, it’s just a ping to localhost. Now that’s a hack you might use in your own status page website to get 100% uptime ;)