Container details
State, resource usage and logs for a single container.
Overview
The container details page covers one container on a monitored host. Open it by clicking a container in the host page's table. It has two tabs: Overview and Logs.
Four stat boxes sit at the top: State, Uptime (how long since the container started), Restarts and Health. A date range selector controls the charts.
Overview tab
Two charts plot the container's resource usage over the selected range, averaged per bucket:
- CPU usage, with the current percentage alongside
- Memory usage, with the current figure in bytes
Below them, Ports lists published ports as hostIp:publicPort -> privatePort/protocol, or the private port alone where nothing is published. Volumes lists mounts as source -> destination. Both say so when there is nothing to show.
State is one of Docker's seven container states: created, running, paused, restarting, removing, exited or dead. Where a container defines a Docker healthcheck, health reads as healthy, unhealthy or starting. A container with no healthcheck reports none, which is not a fault.
CPU and memory are collected for running containers only, so a stopped container reports zero instead of its last known usage.
Logs tab
The Logs tab shows the lines collected for this container, with a header giving the count of recent lines and how long ago they were collected. It refreshes every 10 seconds while the tab is open.
- Each line shows its timestamp in your timezone, the stream it came from and the text.
stdoutis green,stderrred. - Load older logs pages backwards through what is retained, 20 lines at a time and up to 50 per request
- Beginning of retained logs marks the oldest line still stored
- Lines longer than 4096 bytes show a truncation marker
Where lines were written between checks and missed, the page marks the gap with "Some log entries were skipped".
The logs view has no search, no filtering and no severity levels. Checkmate stores the timestamp, the stream and the text as the container wrote it.
Only administrators can view container logs. Other roles see the page but not the log contents.
When the Logs tab is empty
Three cases look similar and mean different things:
- Log collection is off for this host — container logs are not enabled on the monitor. Use Configure monitor to turn them on. Capture hosts cannot collect logs at all.
- No logs collected yet — collection is on, but no check has run since. Only output written after collection was turned on is stored.
- Could not load logs — the request failed. Retry, then check that the host is still reachable.
- You don't have access to container logs — logs are restricted to administrators.
Retention
Collected lines are kept for 7 days and then deleted automatically. The period is fixed and not configurable. Up to 200 lines per container are read on each check, so a container that writes more than that between checks will have gaps.