# Operate an Uptime Kuma monitor Review monitor coverage, target ownership, alert routing, and false-positive handling. Check the named site's prerequisites, task result, backup scope and recovery handoff with xCloud. Canonical: https://xcloud.host/use-cases/operations/operate-an-uptime-kuma-monitor/ Published: 2026-09-30 · Updated: 2026-09-30 · Technical review: 2026-09-30 Evidence: Source reviewed; no production deployment test claimed Editorial owner: xCloud editorial Intent: Review monitor coverage, target ownership, alert routing, and false-positive handling. For: site-owner, administrator ## Requirements and responsibilities - Name the team, server, hostname, owner and affected users for the Uptime Kuma application. Record the current version and the actual business flow that must survive the change. Confirm the current dashboard form, plan eligibility, and server capacity before committing a resource change. A one-click catalog listing is discovery, not permission or proof that the connected MCP profile can install it. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/); [Docker backup operations and storage constraints](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/skills/sites/reference/docker-backups.md); [xCloud One Click Apps catalog](https://xcloud.host/one-click-apps/) - Prepare a non-sensitive test input and an acceptance record. Keep access to the app administrator and an independent observer where possible; omit secrets from AI prompts and client reports. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/); [Docker backup operations and storage constraints](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/skills/sites/reference/docker-backups.md); [xCloud One Click Apps catalog](https://xcloud.host/one-click-apps/) - For a Docker app, identify persistent volumes, bind mounts, external databases and app-level export requirements. A Docker backup briefly stops the app, and an in-place restore replaces current state. Agree a maintenance window and owner before any action that interrupts the service or overwrites data. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/); [Docker backup operations and storage constraints](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/skills/sites/reference/docker-backups.md); [xCloud One Click Apps catalog](https://xcloud.host/one-click-apps/) ## Illustrative situation Uptime Kuma shows green checks for a WordPress site, but the on-call engineer never received the last outage alert. The owner must test notification routing and coverage. ## Choose the approach - Monitor status and notification delivery are separate checks. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/); [Docker backup operations and storage constraints](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/skills/sites/reference/docker-backups.md); [xCloud One Click Apps catalog](https://xcloud.host/one-click-apps/) - A monitor on the same failing host may disappear with the service it is supposed to observe. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/); [Docker backup operations and storage constraints](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/skills/sites/reference/docker-backups.md); [xCloud One Click Apps catalog](https://xcloud.host/one-click-apps/) ## Dashboard and application procedure ### 1. Inventory current monitors **Where:** Uptime Kuma dashboard **Permissions:** Authorized Uptime Kuma application administrator or delegated role with rights for this task; hosting access alone is insufficient. **Inputs:** Targets, intervals, retry rules, status pages **Action:** List business URLs and expected response rules. Identify monitors that only check a cached homepage. **Expected result:** A coverage table. **Verify:** Open target URLs signed out and compare configured hostnames. **If it fails:** If important flow is absent, create a separate task-specific probe plan. Capability: Configure and test Uptime Kuma in its application UI Sources: [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods) ### 2. Review notification route **Where:** Uptime Kuma Notifications **Permissions:** Authorized Uptime Kuma application administrator or delegated role with rights for this task; hosting access alone is insufficient. **Inputs:** Channel, recipient, escalation schedule **Action:** Check each monitor has the intended notification, enabled state and on-call recipient. Test the channel's built-in send function. **Expected result:** A route to a real person. **Verify:** Confirm recipient sees test message and timestamp. **If it fails:** If provider rejects it, repair credentials or channel before trusting alerts. Capability: Configure and test Uptime Kuma in its application UI Sources: [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods) ### 3. Test safe down/recovery **Where:** Dedicated test endpoint **Permissions:** Authorized Uptime Kuma application administrator or delegated role with rights for this task; hosting access alone is insufficient. **Inputs:** Approved window, observer, probe URL **Action:** Point a test monitor at a dedicated endpoint, simulate down and return, and observe both notification events without touching production checkout. **Expected result:** Measured alert delay and resolution behavior. **Verify:** Compare event time to messages received. **If it fails:** If alert is missing, inspect retry thresholds and notification association. Capability: Configure and test Uptime Kuma in its application UI Sources: [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods) ### 4. Check monitor independence **Where:** xCloud server inventory **Permissions:** Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud. **Inputs:** Monitor and target server IDs, DNS **Action:** Compare placement and external network route. Document any shared failure domain or backup dependency. **Expected result:** Known monitoring blind spots. **Verify:** Ask how an alert would arrive if the monitor server failed. **If it fails:** If co-located, add an independent host-level signal. Capability: Confirm requirements and inspect resources Sources: [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/); [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods) ### 5. Set maintenance and backup owner **Where:** Uptime Kuma maintenance/status controls; xCloud Backup **Permissions:** Authorized xCloud team/site operator with the discovered write scope for this exact operation and owner approval for its target and interruption. **Inputs:** Recipients, status page exposure, backup row **Action:** Document who updates checks after URL changes, who declares maintenance and where configuration is backed up. **Expected result:** A maintained monitor service. **Verify:** Check Completed backup and next test date. **If it fails:** If notification owner leaves, reassign before next incident. Capability: Create and inspect Docker backups Sources: [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/); [Docker backup operations and storage constraints](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/skills/sites/reference/docker-backups.md); [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods) ## Maintenance - Review this task after app or template updates and at the cadence agreed with the owner. Record failures as dated observations rather than assuming host health proves service health. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/); [Docker backup operations and storage constraints](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/skills/sites/reference/docker-backups.md); [xCloud One Click Apps catalog](https://xcloud.host/one-click-apps/) - Watch access changes, backup completion, free storage and external providers. Recheck integrations after credential, DNS, mail or source-data changes. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/); [Docker backup operations and storage constraints](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/skills/sites/reference/docker-backups.md); [xCloud One Click Apps catalog](https://xcloud.host/one-click-apps/) ## Recovery decisions - If an alert is missing or false, inspect monitor target, retries and notification route; confirm the real recipient can receive a controlled test message. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/); [Docker backup operations and storage constraints](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/skills/sites/reference/docker-backups.md); [xCloud One Click Apps catalog](https://xcloud.host/one-click-apps/) - Use another independent signal until monitoring is repaired. Restore monitor app state only if its data is damaged and verify notification routing afterward. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/); [Docker backup operations and storage constraints](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/skills/sites/reference/docker-backups.md); [xCloud One Click Apps catalog](https://xcloud.host/one-click-apps/) ## AI handoff Connect an authorized xCloud MCP profile and discover its exact tools and team scope. The packaged REST wrapper is GET-only; use dashboard or app controls for undocumented writes. ### Supported scope - **Confirm requirements and inspect resources** (mcp; read): Discover the connected profile and operation schema first; only teams granted to the connection are visible. Checkpoint: Confirm exact team, server and site identity. Use dashboard\_url returned by the resource; do not invent a dashboard link. Operation identifiers to discover: teams.index, servers.show, sites.show. Scopes: read:servers, read:sites. Sources: [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ### Copyable agent brief ```text Read monitor app host, target site and backup state. Return correlated-failure risks. Do not claim MCP configures monitors or sends alerts; the app owner tests a dedicated endpoint and actual recipient. ``` ### Manual checkpoints - Approve exact site, target, cost and any write or maintenance window after inspecting the proposed plan. - An authorized Uptime Kuma administrator must configure and test app users, content, integrations and business rules in the app. - Native WordPress staging, backup schedule/settings, push/pull and all restores are dashboard-only; Docker restore is dashboard-only and replaces state. - Reconcile data created after the chosen recovery point before any destructive restore. ## Feature coverage - **monitor-ops decision, evidence and task action** (covered): The procedure identifies the authorized task boundary and observable result. Steps: step-1, step-2, step-3, step-4 - **backup, ongoing operation and recovery** (covered): Recovery and maintenance are checked in the task procedure. Steps: step-4, step-5 ## Sources - [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) — reviewed 2026-09-30; v4.4.2 package; xCloud v2.8.8 capability review - [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs) — reviewed 2026-09-30 - [Uptime Kuma notification methods](https://github.com/louislam/uptime-kuma/wiki/Notification-Methods) — reviewed 2026-09-30 - [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/) — reviewed 2026-09-30 - [Docker backup operations and storage constraints](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/skills/sites/reference/docker-backups.md) — reviewed 2026-09-30; v4.4.2 - [xCloud One Click Apps catalog](https://xcloud.host/one-click-apps/) — reviewed 2026-09-30 ## Continue [Explore all use cases](https://xcloud.host/use-cases/) - [Back up and recover a Docker application](https://xcloud.host/use-cases/operations/docker-backup-and-recovery/)