Monitoring: containers, resources and health

Monitoring, under Run, is every container of the organization in one place, in four tabs. It needs no switch: everything here comes from the state each supervisor reports on its check-in.

Containers is the full list, with app, fleet, release, status, CPU and memory, the last day's health and the last check-in; filter by app, fleet or status, or search. The Needs attention count on the Overview and in the header lead here.

Monitoring, Containers tab: four containers across two fleets with their app, release, status, CPU and memory and a health sparkline, with app, fleet and status filters — Containers: every container, filtered by app, fleet or status.

Resources is CPU and memory across the organization: how many containers report, the averages, the top consumer, and a table sorted by CPU or memory with each container's usage over the last hour, six hours or day. Platforms and supervisor versions are counted at the bottom, which is where to see which containers still run an older supervisor.

Monitoring, Resources tab: reporting count, average CPU and memory and the top consumer, then one row per container with a CPU sparkline, memory used of its limit and last seen — Resources: CPU and memory per container, sortable, over the window you pick.

Health charts container health and stable adoption over the last day, week or two weeks, lists every container that needs attention with the reason (unhealthy, failed, exited, out of memory, rolled back, needs redeploy, offline) and since when, and carries the activity, release adoption and event timeline that used to sit on the Overview.

Monitoring, Health tab: a container health chart and a stable adoption chart over the last 24 hours, the needs-attention list, and the activity chart — Health: what is unhealthy, offline or rolled back, and the history behind it.

Telemetry is the fourth tab: the metrics your apps declare, across every fleet. See Telemetry and metrics.

← fleetwide digest Telemetry →