Container Dashboard
Active Containers
CPU usage across the host
What is using it right now.
- api-server87 percent
- postgres-db12 percent
- monitoring6 percent
- everything else9 percent
- Host total68 percent
One container is using most of it. Vigil AI can tell you why in plain words.
Memory in use
Of 32 GB on this host.
- postgres-db4.2 GB
- api-server2.8 GB
- monitoring1.1 GB
- everything else1.6 GB
- Free22.3 GB
In the full version you set a ceiling per container so one of them cannot take the host down.
nginx-proxy
nginx:latest, running for 14 days.
- CPU2.1 percent
- Memory128 MB
- Ports80, 443
- Restarts0
- Health checkpassing
In the full version this opens the logs, the shell and the restart controls for this container.
postgres-db
postgres:15, running for 14 days.
- CPU8.4 percent
- Memory4.2 GB
- Ports5432
- Connections38 of 100
- Last backup4 hours ago
Backups and connection limits are set per container in the full version.
redis-cache
redis:7-alpine, running for 14 days.
- CPU1.2 percent
- Memory512 MB
- Ports6379
- Hit rate94 percent
- Evictions today0
A falling hit rate usually means the cache is too small for what you are asking of it.
api-server
node:20-slim, high CPU for 22 minutes.
- CPU87 percent
- Memory2.8 GB
- Ports3000
- Requests per minute1,240
- Started climbing22 minutes ago
Ask Vigil AI about this one. It reads the logs and the metrics together and says what changed.
worker-1
python:3.11, stopped 3 hours ago.
- Exit code137, out of memory
- Memory limit1 GB
- Peak before stopping1.02 GB
- Restart policynone
- Queue waiting412 jobs
Exit code 137 means the container was killed for using too much memory, not that it crashed.
monitoring
grafana/grafana, running for 14 days.
- CPU4.6 percent
- Memory1.1 GB
- Ports3001
- Dashboards12
- Alert rules28
Your own dashboards keep working. Stockyard sits next to them, it does not replace them.