All features
Docker container monitoring

Docker container monitoring that catches crashes your restart policy hides

The server agent reports every container on the host each minute: its state, health, exit code, restarts, CPU and memory. You're alerted when one crashes or turns unhealthy, and the containers that matter most can be monitors of their own, with uptime history and text or call alerts.

A server's Docker containers: one killed for running out of memory, the rest healthy

Every container, no setup per container

Install the server agent with --docker and the server's page lists every container with its status, image, CPU, memory and restarts.

Crashes that restart policies hide

A container that crashed and came straight back still alerts, with the exit code. A clean docker stop doesn't.

One click to watch a container closely

Click Monitor next to a container and it becomes its own monitor: up while it runs and passes its health check, with uptime, incidents, status pages and SMS or call alerts.

See it in Spot Downtime

The real app, with a demo team's monitors. Included on every plan, Free too.

A Docker container monitor that is down because the container ran out of memory
One container as its own monitor, with uptime, incidents and SMS or call alerts.

Why containers need their own monitoring

A container can fail without the website going down. A queue worker exits, a scheduled job's container stops, a sidecar runs out of memory: the homepage still loads, so an uptime check stays green while orders pile up unprocessed.

Restart policies make it harder to notice. With restart: always or unless-stopped, a crashed container is back in seconds. That keeps things running, but a container that crashes every hour, or loops forever, never shows up anywhere unless something is watching its exit codes and restarts.

What Spot Downtime watches

The server agent reads Docker Engine on the host every minute: each container's state, health check result, exit code, whether the kernel killed it for memory, how many times it has restarted, and the CPU and memory of running ones. The server's page lists them, problems first.

You're alerted when a container exits with an error code, is killed for running out of memory, is stuck restarting, crashed and was restarted since the last report, is dead, or fails its health check. Exit code 0 and the signals docker stop sends count as a clean stop, so deploys don't alert. An alert resolves once the container has run normally for two minutes, so a crash loop sends one alert, not one a minute.

A monitor for the containers that matter

For your most important containers, click Monitor in the server's Containers table, or add a Docker container monitor. It's up while the container runs and passes its health check, and down with the reason when it doesn't, such as 'the container exited with code 1'. It has its own uptime history and incidents, can be shown on a status page, and alerts by every channel, SMS and phone calls included.

If the server itself stops reporting, its container monitors go down too, so a host that disappears never leaves its containers looking healthy.

Read-only by design

Reading Docker's socket requires the docker group, which can control Docker, so the agent only joins it when you install with --docker. The agent itself only lists and inspects containers and reads one-shot stats: it never starts, stops, or changes anything, opens no ports, and sends its reports out over HTTPS.

How to set it up

  1. 1Add a server monitor and run its install command on the host with --docker.
  2. 2Within a minute, the server's page lists every container.
  3. 3Click Monitor next to the containers that matter, or add one under Add monitor → Docker container.
  4. 4Choose how to be alerted, like any monitor.

The details

Reported
Every container's state, health, exit code, OOM kills, restarts and restart policy; CPU and memory of running ones
Server alerts
A container exits with an error code, is killed for memory, keeps restarting, crashed and was restarted, is dead or fails its health check
Not alerted
Exit code 0 or the signals docker stop sends; containers you ignore by name or pattern, like backup-*
Container monitors
Up while running and passing its health check; down with the reason otherwise, or when the server stops reporting
Requirements
The Linux server agent 1.1.0 or later, installed with --docker
Plan
Every plan. Each container monitor counts as one monitor

Questions

Why does the agent need --docker?
Reading Docker's socket needs the docker group, and that group can control Docker, so the install script only adds the agent to it when you ask. The agent itself only lists, inspects and reads stats; it never starts, stops or changes a container.
What's the difference between the server's container alerts and a container monitor?
Every container on a server gets alerts through your chat, email, PagerDuty and webhook channels, without any setup. A container monitor is for the ones that matter most: it has its own uptime and incidents, can go on a status page, and alerts by every channel including SMS and calls.
Will stopping a container on purpose alert me?
Not from the server's container alerts: exit code 0 and docker stop's signals count as a clean stop. A container monitor does go down whenever its container isn't running, since that's what it's watching; pause it or schedule maintenance first.
What about Docker Compose names like shop-web-1?
Containers are matched by name, as docker ps shows it. If you recreate a container under a new name, edit its monitor to the new one; the server's Containers table shows the current names.
Does it work with Kubernetes?
Not yet. The agent reads Docker Engine on the host. For Kubernetes, monitor your services' endpoints with website, API or TCP checks.

Set up docker container monitoring in under a minute

Included on the Free plan. No card needed.

Create a free account