Checkmate

Docker host details

The host page, its container table and what the counts mean.

Overview

Each Docker monitor has a host page listing every container the daemon reports. Open it from the Docker page in the sidebar by clicking a row in the monitors table.

The monitors table shows two columns: Host and Containers, where the container count reads as "3 of 5 running".

Stat boxes

Four counts sit at the top of the host page:

  • Containers — every container the daemon reports, running or not
  • Running — containers in the running state
  • Stopped — containers in the exited or dead state
  • Unhealthy — containers whose Docker healthcheck reports unhealthy
Note

The Stopped count includes containers that exited cleanly with code 0. The container alert rule does not, so a host can show a stopped container here without being marked breached. Alerts treat a clean exit as a finished one-shot job.

Container table

The table lists containers with these columns:

  • Containers — the state, the container name and its image
  • Status — the container's Docker state
  • Health — the healthcheck result, or none where the container defines no healthcheck
  • CPU — CPU percentage at the last check
  • Memory — memory percentage at the last check
  • Restarts — the container's restart count

Click a row to open that container's details page.

The table shows the most recent check only, so there is no date range on this page. Use a container's details page for history.

Host status

The host is a monitor like any other, so it has a status and an uptime history. Up and down track whether the daemon answers, not what the containers are doing.

If you enable either container alert on the monitor, the host is marked breached while any container breaches the rule, shown as "alert" in the monitor list. It recovers when every container is back within the rules. Without those settings enabled, container problems are visible on this page but do not change the host's status.

A host that is down suppresses container breaches, because Checkmate has no current container data to judge.

See also

On this page