Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.augustin.ai/llms.txt

Use this file to discover all available pages before exploring further.

Health monitoring across three layers: is the container running, is the app internally functional, and is it reachable externally.

Tools

  • Homepage — dashboard with container status, internal site monitors, and per-service API widgets. Talks to the swarm API via docker-socket-proxy_dockerproxy on the swarm overlay, so it sees services scheduled on both nodes.
  • Uptime Kuma — external HTTP checks against public URLs, with Telegram alerting.
  • Dozzle — log aggregation across both nodes (mode: global swarm service).

Coverage Matrix

ServiceContainer StatusInternal FunctionalityExternal Reachability
aiclient2apiHomepageDocker healthcheck (healthcheck.js)Kuma
audiobookshelfHomepageDocker healthcheck + widgetKuma
bazarrHomepageDocker healthcheck + widgetKuma
bulwarkHomepage/api/health via healthcheckKuma
calibre-webHomepageDocker healthcheck + widgetKuma
chaptarrHomepageDocker healthcheckKuma (/ping)
cloudflaredHomepageCloudflare API widget (external)— (implicit; if down, every public URL fails)
docker-socket-proxyHomepage— (internal only)
dozzleHomepageKuma
drawHomepagePort check onlyKuma
elementHomepageDocker healthcheckKuma
flaresolverrHomepageDocker healthcheck (sessions.list probe)Kuma
gluetunDocker healthcheck + Homepage API widget (real VPN status)Kuma (control server only)
homepageHomepageDocker healthcheckKuma
jellyfinHomepageWidget (no healthcheck)Kuma
matrix-db (postgres)HomepageDocker healthcheck
mautrix-discordHomepage
minifluxHomepageDocker healthcheck + widgetKuma
miniflux-db (postgres)HomepageDocker healthcheck
n8nHomepageKuma
nextfluxHomepagePort check onlyKuma
openclawHomepageDocker healthcheck (/healthz)Kuma
openwebuiHomepageDocker healthcheckKuma
pocket-idHomepageDocker healthcheckKuma
prowlarrHomepageDocker healthcheck + widgetKuma
qbittorrentHomepageDocker healthcheck (via gluetun)— (behind VPN, only through seerr)
radarrHomepageDocker healthcheck + widgetKuma
reader/feed-scraperHomepage
reader/rsshubHomepageKuma
registryHomepage— (internal only)
searxngHomepageKuma
seerrHomepageDocker healthcheck + widgetKuma
sonarrHomepageDocker healthcheck + widgetKuma
stalwartHomepageHomepage JMAP widget (real query)Kuma
synapseHomepageDocker healthcheckKuma (accepts 401/403)
traefikHomepageHomepage API widgetKuma (accepts 401)
uptime-kumaHomepageDocker healthcheckKuma
yamtrackHomepageDocker healthcheckKuma
yamtrack/redisHomepage

Drive Monitoring

scripts/drive-check.sh runs on i3 every 15 min via cron. For each drive + the mergerfs pool, it checks mountpoint status, read, and write — then pushes explicit status=up or status=down to its Uptime Kuma push monitor. Missing pushes still trip the monitor after its heartbeat interval, but a failure is surfaced immediately. Monitored drives: sandisk-2tb, sandisk-1tb-lg, sandisk-1tb-dg (pool members), mergerfs-pool (/mnt/main/media).

Backup & Maintenance Push Monitors

Every cron script that matters pushes to Uptime Kuma — up on success, down with a message on any failure. Tokens live in scripts/.kuma-env (gitignored, symlinked/synced to Pentium).
ScriptNodeFrequencyPush token
scripts/backup-i3.shi3daily 03:00PUSH_BACKUP_I3
scripts/backup-pentium.shPentiumdaily 04:00PUSH_BACKUP_PENTIUM
scripts/restic-check.shi3weekly Sun 05:00PUSH_RESTIC_I3, PUSH_RESTIC_PENTIUM
scripts/rebuild-images.shi3weekly Sun 04:00PUSH_REBUILD_IMAGES
aiclient2api/sync-kiro-token.pyi3every 15 minPUSH_KIRO_SYNC
scripts/drive-check.shi3every 15 minper-drive tokens
Unset tokens are a no-op — the script still runs and logs normally. To enable alerting, create a push monitor in Uptime Kuma and paste its ID into .kuma-env.

Gaps

  • Healthchecks still missing on: cloudflared, docker-socket-proxy, dozzle, draw, jellyfin, n8n, qbittorrent, registry, traefik, mautrix-discord, feed-scraper, nextflux, rsshub, searxng, stalwart, yamtrack/redis. Most of these ship no healthcheck upstream; a few could use a cheap curl-based one added in our compose file.
  • Cloudflared has no external monitor. Its status is implicit — if the tunnel is down, every public-URL Kuma check fails at once.
  • Gluetun’s Kuma monitor only confirms the control server responds. Homepage’s widget (with API key) gets the real VPN-tunnel state.
Cheapest wins: add Docker healthchecks to draw, stalwart, n8n, and searxng. All have trivial HTTP endpoints.