N8n Monitor

**Quick judgement** A focused, lightweight monitoring skill for self-hosted n8n instances running in Docker. It is well-suited for operators who need fast insights into container status, recent logs, health, and CPU/memory usage without deploying a full monitoring stack. **What it does well** - Uses standard Docker commands (`docker ps`, `docker logs`, `docker inspect`, `docker stats`) to gather operational data. - Read-only behavior (no restarts or mutations), which reduces operational risk. - Outputs in Markdown with simple tables and clear status indicators, making it easy to scan. - Good fit for local/server environments where the assistant has Docker CLI access and n8n runs in a container. **Key limitations & risks** - Assumes Docker is installed, accessible from the runtime, and that the n8n container is named `n8n`; different naming or orchestration (e.g., Docker Compose with other names, Kubernetes) will break or reduce usefulness. - `docker ps | grep n8n` can be brittle if multiple containers match the pattern or if the name differs. - Log access (`docker logs --tail 50 n8n`) may expose sensitive data present in n8n logs (e.g., workflow payloads, tokens) to the assistant or any consumers of the output. - Depends on the container having a defined healthcheck for meaningful health status via `docker inspect`. **Recommended scenarios** - You run a **single or small number of n8n containers via Docker** on a host where the assistant can execute Docker commands. - You want a **fast operational snapshot** (up/down, health, logs, CPU/memory) for manual troubleshooting or periodic checks. - Environments where you **control data sensitivity** and are comfortable exposing n8n logs and resource stats to this monitoring flow. **Less suitable for** - Kubernetes, Swarm, or more complex orchestrated environments where Docker CLI monitoring is insufficient. - Highly regulated or sensitive environments where log contents may contain confidential data and must be tightly controlled. - Advanced observability use cases requiring metrics time series, alerting, or historical analysis beyond simple snapshots.