A container that crashes and restarts every few minutes can look healthy from outside. Docker monitors will watch your containers from the inside and alert you to crashes, restart loops and failing health checks.
Containers make deployment easy and failure quiet. A worker crashes on bad input and Docker restarts it, again and again; a container runs out of memory and gets killed; a health check fails for hours while the port still answers. From the outside, everything looks up.
Docker Monitoring will watch the containers on your hosts and alert you to crashes, restart loops, failing health checks and containers running out of resources.
The plan for the first release. Every check will be stored in a full log, like all Upzilla monitors.
Running, stopped, exited and paused containers.
Restart loops and crashes, with the exit code.
Containers whose own health check fails.
CPU and memory per container.
TCP and HTTP monitors can already check the ports and endpoints your containers expose.
Set up like every other Upzilla monitor, in a few minutes.
On each Docker host.
All of them, or by name or label.
When a container stops, loops or runs out of memory.
Production without a full monitoring stack.
Watch the containers behind your tools.
Client servers running Docker Compose.
Queues and jobs that run in containers.
The same alert channels as every Upzilla monitor, as many as you like.
We are building it as part of the next Upzilla; many new features arrive before the new year. Create a free account to hear first.
Yes, containers started by Compose will be monitored like any other.
TCP and HTTP monitors can already check the ports and endpoints your containers expose, and the Cron Jobs Monitor can watch scheduled jobs.
The first release is for Docker hosts. Tell us if you need Kubernetes — requests shape what comes next.
Start with 10 free monitors today — we will tell you the moment this one is ready.