Server Guide

Monitor Your Services with Uptime Kuma: A Beginner's Guide

Published on March 22, 2026

Monitoring often seems optional until the first outage happens at the worst possible moment. If you run a website, an API, a game server, a mail service, or a small Docker stack, you want to know quickly when something stops responding.

Uptime Kuma is a convenient way to fill this gap without setting up a large monitoring system on day one. It is easy to self-host, simple to understand, and flexible enough to monitor different service types in a single dashboard.

In this article, I focus on getting started quickly: creating meaningful checks, adding notifications via Discord and Pushover, and keeping Prometheus and Grafana in mind for future monitoring stack expansion.

Why Uptime Kuma is a Good Starting Point

It provides a clear dashboard, enough check types for most real-world setups, and alerting that easily integrates with the tools you already use.

HTTP and HTTPS Endpoints

Monitor websites, APIs, login pages, and health endpoints with status code checks, keyword matching, and response time history.

TCP Ports and Game or App Services

Monitor raw TCP services like SSH, mail, databases, custom applications, or anything that should respond on a port.

Ping for Host Reachability

Check if a machine is reachable before a specific application check fails.

Docker Containers and Internal Services

Keep an eye on self-hosted apps that are not public but still critical for backups, queues, or admin tools.

A Small Setup Brings Real Benefits

You don't need a complicated rollout. An Uptime Kuma instance and a short list of important checks already significantly improve your response time when something goes down.

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

Deploy Uptime Kuma via Docker Compose on a small server or alongside your existing services.
Add monitors one by one, starting with the services where a silent failure would cause the most damage.
Use sensible intervals and retry settings to avoid unnecessary noise from short network fluctuations.
Group monitors by project or environment to keep the dashboard organized as it grows.

Notifications Make Monitoring Truly Useful

A dashboard is helpful, but alerts turn monitoring into concrete action. Uptime Kuma supports many targets, and Discord plus Pushover is a simple combination for small teams or individuals.

Discord

A Discord webhook is quick to set up and works well for team-wide alerts in a shared Ops channel.

Pushover

Pushover is convenient for direct notifications to your phone, ensuring you receive alerts even when away from your desk.

A good default is to also send recovery messages, so you know whether the issue has been resolved or if manual intervention is still required.

What to Monitor First

Start with the parts that have the most real impact. Usually, this is the public endpoint, the admin or API interface, and an additional simple reachability check for the host itself.

Monitor from the user's perspective whenever possible. A homepage or API health check often tells you more than just the status of a container.
Use tags or names that make incidents understandable at a glance, especially when staging and production exist side by side.
Send alerts to more than one place if availability is important, for example Discord for the team and Pushover for direct escalation.
Check recurring alerts instead of just acknowledging them. Repeated noise often means the check or service should be adjusted.

Prometheus and Grafana are the natural next step

If you later want dashboards, longer retention, or combined infrastructure metrics, Uptime Kuma can support this path as well. Monitoring data can be exported to Prometheus and then visualized in Grafana.

At this point, a lean uptime view becomes a broader observability setup. If you want to see the Prometheus and Grafana part in more detail, I have already covered this stack in a separate post.

Read the post on monitoring with Prometheus and Grafana

Keep It Simple and Actionable

The best monitoring setup is usually the one you actually maintain. Uptime Kuma is great if you want quick visibility into websites, services, and servers without diving into a heavy stack right away.

Start with a small number of monitors, integrate Discord and Pushover, and only expand to Prometheus and Grafana when you really need deeper metrics and dashboards.