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:
1 parent
0fa50c2d5a
commit
12f2662465
10 files changed
+502
-5
No files matched your search
@@ -56,6 +56,7 @@ the dashboard views themselves load fine. (UniFi, Nginx Proxy Manager, Home Assi
|
||||
- **Auth:** Bearer token against Dockhand's own API
|
||||
- **Actions used:** list environments/containers, check for image updates, start/stop/restart a container
|
||||
- **Required access:** A Dockhand API token belonging to a user with access to every environment (Docker host) you want visible, with permission to **start/stop/restart containers and trigger update checks** in each — not just view them.
|
||||
- **Suggested checks:** each container's image and published ports are also used to suggest an endpoint check on the app's own health address ([MONITORING.md](docs/MONITORING.md#endpoint-checks-and-heartbeats)). Ports are read from whatever shape Dockhand's container list carries them in (Docker's own, `"0.0.0.0:8080->80/tcp"` strings or inspect's map) — **not checked against a live Dockhand**; if none is read, the Docker host's listening ports from its agent stand in.
|
||||
- **Container health:** on the 15-minute health pass the app also reads every container's state and status text and raises alerts for what is broken — see [Docker containers that are broken](docs/MONITORING.md#docker-containers-that-are-broken). A Docker host that Dockhand
|
||||
cannot read (its Hawser agent is down) is an alert too, and its containers' alerts are held, not cleared. The Docker page shows each container's problem and has a **Leave alone** button.
|
||||
|
||||
|
||||
Reference in new issue
Block a user