As our Home Lab and the associated network become more complex, monitoring the operational status of our services and equipment becomes essential. We use a tool called Uptime Kuma to monitor the operational status of our home lab. This tool can monitor various types of equipment and services, providing multiple mechanisms to notify us when a service is unavailable.
Uptime Kuma Docker Install
We deployed this tool as a Docker container in our Docker cluster. It is easy to install and configure. We used the following video to help with the installation –
Monitor Local and Remote Docker Hosts
Uptime Kuma can be used to monitor the health of Docker containers running on Local and Remote Docker Hosts.
The Local Docker Host can be monitored by binding /var/run/docker.sock to the Uptime Kuma container.
Some additional configuration is required on Remote Docker Hosts to expose Docker information.
The process for setting up both of the cases is covered here.
Performance and Backups
The tool’s database is sensitive to the volume store used to contain its database. For this reason, we bound Uptime Kuma’s present volume to storage inside the Docker Host VM instead of using our high-availability network store.
We also used the root crontab to back up the local VM configuration data to the Docker volume on our high-availability store as follows:
# Backup local VM configuration for uptime kuma
# to HA docker volume
*/15 * * * * /usr/bin/rsync -r --delete \
/home/ubuntu/uptime-kuma/ \
/home/ubuntu/docker/uptime-kuma/data