Docker container monitoring alongside your host
See which containers are running, how much CPU and memory they use, and whether their health checks are passing. System Stats brings Docker and machine metrics into the same dashboard.
| Container | State | CPU | Memory |
|---|---|---|---|
| nginx-proxy | running | 2.4% | 128 MB |
| postgres-db | running | 8.1% | 512 MB |
| app-worker | exited | — | — |
What you can monitor
Resource usage
Track CPU, memory, network traffic and disk I/O for each container. Compare a busy container with host resource usage when investigating contention.
State and health
Inspect running and stopped containers, ports and health status. A container without a Docker health check cannot report application health through that check.
Logs and controls
Stream container logs and use supported start, stop, restart and pause actions from the dashboard when agent remote control is enabled.
Connect your Docker host
1. Install on the Linux host
Create a System Stats account, then install statsd on the machine running Docker. A native installation can inspect both the host and its local containers.
Terminalcurl -fsSL https://linux-stats.com/install.sh | sh sudo statsd login sudo statsd status2. Authorize and check socket access
Open the login link, approve the machine, and keep the CLI and service on the same configuration directory. The service must be able to access the local Docker socket.
3. Check collection and open the dashboard
Use local diagnostics to investigate missing Docker metrics, then confirm containers appear in your dashboard. Local diagnostics alone do not confirm delivery.
Terminalsudo statsd doctor sudo statsd interval docker
Docker requirements and collection
Requires a local Unix socket at /var/run/docker.sock or /run/docker.sock and Docker API 1.44 or newer. The default collection interval is 3s; saved intervals can be changed with statsd interval docker.
When running statsd in Docker, the agent only sees resources exposed to its container. The basic Compose installation does not mount the Docker socket or host filesystem. Use the Docker installation guide for the optional socket mount.
Docker socket access permits API operations even when the socket is mounted with :ro. To disable dashboard commands while keeping metrics, run sudo statsd disable-control with the service configuration directory.
Docker Desktop runs containers inside a VM. Container metrics do not describe the underlying macOS or Windows host, and the Windows named pipe is not a supported Unix socket.
Explore monitoring for your systems
Proxmox monitoring →
Keep Proxmox guest state and resource usage beside the machine that runs them. Install statsd on the node to discover virtual machines and LXC containers through the local Proxmox tools.
Linux server monitoring →
Monitor Linux servers, ARM machines and Raspberry Pi from one dashboard. The statsd agent runs as a background service and collects the system metrics you need to investigate resource pressure.
HTTP uptime monitoring →
Check whether an endpoint responds as expected, how long it takes, and when it becomes unavailable. Keep uptime and response-time history beside the machines and containers behind your service.
Install the agent and see it all
Free up to 5 machines forever. No credit card. Two minutes from landing here to live metrics streaming in.