Build useful Uptime Kuma monitoring by defining one clear service target, selecting a protocol your version supports, setting an expected success condition, and testing the notification path.
Start with the service question
Write the question each monitor should answer: is a public page reachable, is a TCP service accepting connections, or is a private endpoint returning the expected health signal? Give every monitor a name that identifies the service and environment. One focused question is easier to investigate than a check that mixes unrelated dependencies.
Choose a supported monitor type
In your Uptime Kuma web interface, select the protocol that matches the target and the version of Uptime Kuma you run. HTTP or HTTPS checks suit web endpoints, while TCP or ping checks suit services that expose those signals. Enter the host, port, or URL exactly as the service expects, and avoid publishing credentials in a monitor field.
Define success precisely
For an HTTP monitor, decide whether a successful status code is enough or whether a stable response phrase should also be present. Prefer a small health endpoint that does not require a human login. For other protocols, define the connection or response that proves the service is ready. Test a known-good target and a deliberate failure so the result is understandable.
Make notifications actionable
Choose a notification channel that the responsible people can access and send a test alert before relying on it. Use a concise monitor name in the message, group related alerts, and review the recovery notification as well as the outage notification. If a check is noisy, inspect the target, timeout, and expected response before simply muting it.
Keep the observation path honest
A monitor is most informative when its observation path is not identical to the application it checks. Document where the monitor runs, what it can reach, and which failures it cannot detect. The comparison context helps distinguish an open-source monitoring tool from the specific observation path you choose; it does not define what any account includes.
Check the current project guidance
Uptime Kuma is one of the apps named by opensource.hosting. Use the Uptime Kuma documentation for the version you operate to confirm monitor types, alert channels, update steps, backup options, transport security, and observation limits. These details depend on the project and your configuration; verify them before relying on a workflow. Read the alternative map, review the products page, or use the support ticket form for account-specific questions.