Suggested checks for the apps in your containers

With Dockhand connected, an image the app recognises (about 20 with a health endpoint of
their own, plus a few dozen web UIs) is offered as an endpoint check on that app's own
health address, with what a good answer looks like set up as a value check: Immich's ping
says pong, Nextcloud's status.php is not in maintenance, Gitea's health says pass, and so
on. Asked on the Docker host's address at the port the container publishes. Container
ports are now read from Dockhand's list.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-10-24 21:23:13 +02:00
1 parent 0fa50c2d5a
commit 12f2662465
10 files changed
+502 -5

No files matched your search

+6
View File
@@ -237,6 +237,12 @@ daily summaries for the charts and uptime figures.
- **A header, for an API that wants a token.** A web check can send one header with its request (usually `Authorization: Bearer …`). The value is stored **encrypted** when `CREDENTIALS_ENCRYPTION_KEY` is set, is never sent back
to the browser (the form says *Saved — leave blank to keep it*), and goes only to the address you gave — **not to another host a redirect leads to**.
- What an administrator types in cannot be just anything: loopback, link-local and cloud-metadata addresses are refused, and the connection goes to the one address that passed the check. LAN and public hosts are fine.
- **Apps in your containers.** With Dockhand connected, an image the app recognises (Immich, Paperless-ngx, Nextcloud, Vaultwarden, Authentik, Gitea, Grafana, Prometheus, Jellyfin, n8n, ntfy, Gotify, Nginx Proxy Manager, Open WebUI, Ollama, SearXNG, Wiki.js,
BookStack, Homebox, Semaphore, Meilisearch, and a few dozen with just a web page) is offered as a check on **that app's own health address**, with what a good answer looks like set up as a [value check](#endpoint-checks-and-heartbeats): Immich's
`/api/server/ping` must say `res` = `pong`, Nextcloud's `/status.php` `maintenance` = `false`, Gitea's `/api/healthz` `status` = `pass`, Grafana's `/api/health` `database` = `ok`, Prometheus's `/-/healthy` must contain "Healthy". It is asked on the Docker
host's address — the server the app knows under the Docker environment's name in Dockhand, first usable IPv4 — at the **port the container publishes** (from Dockhand; if Dockhand does not say, the one the host's agent sees listening that the app is known to use).
Only running containers, only hosts the app knows, and only what no check covers already is offered; where an app is recognised the plain "something answers on 8080" suggestion for that port is replaced by it. The paths are those the projects publish for the purpose, **not tried against live
instances here**: a wrong one is a failing check you can edit. Uptime Kuma's monitors are not looked at, so something you already watch there may be offered — *Not for me* stops it.
- The app suggests checks it can already work out (a web port a server's agent sees open, a secret with a host) under *Endpoints → Suggested*, and proxied hosts Nginx Proxy Manager serves.
**Heartbeats** (Monitoring → Heartbeats) are the other direction: a cron job or script **calls an address when it finishes**, and the app alerts when it does *not*. A heartbeat has a **period** and a **grace**; it is