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
@@ -590,7 +590,9 @@ dashboard and in `/metrics`. Results are kept for two weeks, then as hours (four
|
||||
**Suggested checks** (on the Endpoints page, administrators). From what the app already knows it offers checks you could add with a click: a **web port a server's agent
|
||||
sees open** (80, 443, 8080, 8443 — when a server has both the plain and the secure one, the secure one, since it also reads the certificate), under the name DNS gives that
|
||||
server if there is one (an A or AAAA record with one of its addresses, or an alias to it), otherwise its own hostname or address; and a **secret that already reads a
|
||||
certificate**, since a check also hears when the service stops answering. Each is linked to its server. Something a check already covers is never offered, **Not for me**
|
||||
certificate**, since a check also hears when the service stops answering; and, with Dockhand connected, **the apps in your containers**, recognised from their images and checked on each one's own health address with what a good
|
||||
answer looks like — Immich's ping must say `pong`, Nextcloud's `status.php` must not be in maintenance mode, Gitea's health must say `pass`, Grafana's database must be `ok`, Authentik's health endpoint must answer, and so on for about forty
|
||||
apps (the ones with no open health endpoint get a plain "the page answers"). They are asked on the Docker host's address (the server the app knows by that name) at the port the container publishes. Each is linked to its server. Something a check already covers is never offered, **Not for me**
|
||||
stops one being offered (and they can be brought back), and nothing is asked until you add it. Uptime Kuma's monitors are not offered: they are already being watched, and
|
||||
the adapter only keeps a host and port for them, not the address.
|
||||
|
||||
|
||||
Reference in new issue
Block a user