Setting Up Uptime Kuma for Self-Hosted Monitoring

steps

1. Create a directory to hold Uptime Kuma’s configuration:

   bashCopy

   mkdir uptime-kuma  
   cd uptime-kuma  

2. Create a docker-compose.yml file inside this directory with the following content:

   yamlCopy

   version: "3"
   services:
     uptime-kuma:
       image: louislam/uptime-kuma:latest
       container_name: uptime-kuma
       ports:
         - "3001:3001"
       volumes:
         - ./data:/app/data
       restart: always

3. Launch the Uptime Kuma container:

    docker-compose up -d  
    # Output: Creating uptime-kuma ... done  

4. Confirm the container is running:

    docker ps  
    # Output: uptime-kuma | Running | Exposed Port 3001  

steps

1. Open a browser and go to http://<Docker-host-IP>:3001.
2. Create the admin account by setting a username and password.
3. Begin adding monitors by grouping services logically based on criteria such as host type or service function.
4. Save the configuration for efficient management.

steps

1. Add a new monitor by selecting the type, such as:

   • Docker container: Monitor specific containers on a host.
   • HTTP(S): Check web service status.
   • Ping: Test network devices like IP cameras.

2. Adjust the heartbeat interval:

   • Default: 60 seconds.
   • Use a lower interval (e.g., 20 seconds) for critical services.

3. Set retries to reduce false alarms for intermittent downtime. For instance, set retries to 3 for sporadically unstable services.

4. Group monitors logically (e.g., all Docker containers under one group, or services grouped by functionality).

steps

1. Navigate to Notifications in the settings menu.

2. Select a notification method (e.g., Home Assistant, email, SMS).

3. Enter the necessary credentials and test the configuration.

4. Enable default notifications for all monitors or set per-service preferences.

   Example: Configure Home Assistant JSON-based notifications for granular control.

steps

1. Stop a monitored service or Docker container to simulate downtime.
2. Observe if the monitor correctly reflects the downed service in the dashboard.
3. Ensure notification retries and alert thresholds are functioning as configured.
4. Update or fine-tune monitors and notifications based on real-time conditions.