agentleFS
WhispersOfJWhispersOfJ/arrfleet-toolkit/skills/health-monitor/SKILL.md

health-monitor

Skill1 starsChanged 4 months agoMITView on GitHub

Check container-level and HTTP-endpoint health across an Arr-stack docker compose project in one pass — Docker healthcheck status plus a reachability probe for each web-facing service (Arr apps, Plex, request manager, download client, etc). Use for a general "is everything okay" sweep, after a host reboot, after a docker compose up, or when triaging a user report of "the stack seems broken" before diving into any single service. Trigger phrases: "is everything healthy", "check the stack", "what's down", "post-reboot check", "give me a health report".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run from the compose project root, or pass --compose-dir.

    line 29
  2. Very specific:

    Read-only: this skill only observes (docker compose ps, HTTP GET).

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Health Monitor

Two independent signals, both checked, because they catch different failure modes:

  1. Docker healthcheck status (docker compose ps) — catches a container that's crash-looping or whose own healthcheck is failing.
  2. HTTP reachability — catches a container that's "healthy" per Docker but whose web UI/API isn't actually responding (e.g. still booting, or the app deadlocked without dying).

A service can fail either check independently — report both, don't collapse them into a single up/down.

Usage

python3 monitor.py sweep                     # full report: docker health + HTTP checks
python3 monitor.py sweep --json               # machine-readable output
python3 monitor.py docker-only                # skip HTTP checks (faster, useful mid-restart)
python3 monitor.py http-only                  # skip docker inspect (useful outside the host)
python3 monitor.py watch --interval 30        # repeat sweep every N seconds until Ctrl-C

Run from the compose project root, or pass --compose-dir. HTTP checks only run against services actually present in docker compose ps — no false "unreachable" report for an app the project doesn't even run.

Configuring services

monitor.py::DEFAULT_HTTP_SERVICES ships sensible defaults for the common Arr-ecosystem apps (Radarr, Sonarr, Lidarr, Readarr, Prowlarr, Bazarr, Jellyseerr/Overseerr, Plex, Emby, Tautulli, SABnzbd, qBittorrent). To add or override a port/health-path for this project specifically, drop a .arrfleet-health.json next to docker-compose.yml:

{"my-custom-service": [9000, "/healthz"]}

Interpreting results

  • Docker-healthy + HTTP-unreachable: likely still booting (check again in ~30s) or a reverse-proxy/network issue — don't restart immediately, re-check first.
  • Docker-unhealthy: hand off to docker-compose-manager restart <service>, respecting any cascade map that project has defined.
  • Both failing for a mount-owning service's dependents simultaneously (e.g. every Arr app down at once) strongly suggests a FUSE/network mount went stale — check docker-compose-manager cascade-map and the mount owner's own health first.

Safety rules

  • Read-only: this skill only observes (docker compose ps, HTTP GET). It never restarts or modifies anything — hand off findings to docker-compose-manager for remediation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.