Features · Monitoring · Containers
Monitoring · Containers

Docker + Podman,
auto-discovered and watched.

Every container the runtime knows about — its image, its command, its ports, its restart count — surfaced automatically. Per-container CPU + memory + network metrics. Start / stop / restart from the UI with full audit.

docker · 12 running
app-web nginx:1.27 · 2d
app-php php:8.3-fpm · 2d
redis redis:7 · 14d
queue-worker restarts 3 · 4h
mailhog exited 137 · 1d
— Why this matters

The runtime already knows. It just is not telling you.

01

Containers move; hosts do not.

What is running where changes without anyone updating a document. Discovery is the only inventory that stays true.

02

Restart count is the signal people miss.

A container that is up but has restarted eleven times is not healthy, and "up" will not tell you.

— What's included

What comes back per container.

Discovered automatically
Image, status and published ports.
Per-container metrics
CPU, memory, network I/O and PID count.
Remote actions
Start, stop and restart, audited like every other remote action.
Logs
Retrieved without SSHing to the host.
Disk usage
Images, containers and build cache — the three things that fill a disk quietly.
— What it looks like

Per container, not per host.

44% memory limit
Example view · api-worker · last 12 h · the sawtooth is the restart at 03:20
— Works with

Connected capabilities

— FAQ

Questions, answered honestly.

What runtimes are supported? +
Docker (any modern version), Podman 4+, containerd via the standard socket. Kubernetes is monitored separately — see the K8s view.
Can I run actions without root? +
Yes — the agent runs as a member of the docker group. No root needed for the runtime API.
How are env vars protected? +
Allow-list redaction before they leave the host. Common secret-shaped keys (TOKEN, SECRET, PASSWORD) are redacted by default.

Run containers, watch them, restart them.

Container support is part of every plan.

Get early access Back to Monitoring