Monitoring and Docker

These are two separate pages that both answer "what's actually going on across my servers," from slightly different angles: one about resource usage, one about what containers exist.

Monitoring

/monitoring is organized around your nodes, not your services. At the top, a quick summary across everything: how many nodes are online out of how many total, total memory used versus available, total disk used versus available. Below that, a card per node with its own online status, a memory bar, a disk bar, and its one-minute load average.

This data comes from the agent on each node, which reports it back periodically, it isn't Flow polling your servers live on every page load, so what you're seeing is current as of that node's last check-in, which normally lags reality by no more than a few seconds.

For an individual service, there's a much smaller Monitoring tab on its own page, it just shows that one container's current state, status, and image, a quick sanity check rather than a graph. For the fuller picture of resource usage, this page is where you want to be.

Docker

/docker is deliberately a read-only window into every container on every node, grouped by node, each with its status, image, and Docker's own raw status text (things like Up 3 hours). There's no start, stop, or exec control here on purpose, that belongs on the service that owns a given container. This page exists for visibility across everything at once, especially useful for spotting a container that doesn't obviously map to a service you remember creating.

Nodes report their container list roughly once a minute, so a container that just started or stopped may take a moment to show up or disappear here.