Reading the Dashboard

CCD reads many clusters, and at any moment one of them may be unreachable or may not support a feature. Rather than quietly folding that into a total, CCD keeps missing data visible. This page explains what you are looking at when something is incomplete.

A dash is not a zero

A dash means the value is unknown. Zero means CCD read the value and it was zero. A cluster that cannot be reached is left out of a total rather than counted as zero.

Totals say what they cover

Inventory totals, service counts and combined charts show how many clusters contributed when some data could not be read. Fleet capacity goes further: it includes only clusters reporting both used and total space, and shows over N of M clusters under the number, so an incomplete reading cannot produce a misleading fleet percentage. Hover it to see how many clusters were unreachable, lacked the data, or have not been checked yet.

The fleet-wide tables behave the same way. Disks, Pools, HA groups, OSDs, Servers and Services identify the clusters they could not read while keeping the available rows visible. An unreadable inventory is not an empty inventory, and unreadable disk health is not a count of zero failing disks.

Unsupported is not missing

A feature a cluster does not have is reported separately from data CCD failed to fetch. A plain Ceph cluster is named in the Disks view as not supported and left out of the disk counts, rather than adding zero disks to them. Charts work the same way: the Ceph API serves no time series, so there is nothing to draw.

Reachable and healthy are different measurements

A reachable cluster shows Reachable yes in the Clusters table even when its Health is Unknown. Connectivity and health are measured separately, and one does not stand in for the other.

Findings and tasks

Advisor and Tasks distinguish an empty result from unavailable data. Partial results name the clusters they left out. When the finding count is incomplete, the Advisor entry in the navigation turns amber, and hovering it shows N+ open advisories. A recommendations request that failed does not mean the fleet is healthy.

Ceph health checks appear in Advisor. The croit-version comparison leaves out Ceph and demo clusters.

Audit

Audit identifies the clusters whose entries could not be read, including the case where the configured account lacks audit permissions on that cluster. CCD's own entries and the results from available clusters stay visible. Audit is visible to admins only. Being a CCD admin grants no extra permissions on a connected cluster.

Charts

Single-cluster and per-OSD charts distinguish a failed read from a chart that simply has no history yet. A chart that failed explains itself independently, so the others on the page stay usable. A server without samples does not hide the other servers' history in a combined chart. A history containing only missing measurements shows No data, while measured zeros stay visible. Chart colours follow your system theme without a reload.

Capacity thresholds

Nearfull and full counts use the most filled OSD, not the cluster's average usage, because a single full OSD is enough for Ceph to stop accepting writes. Capacity forecasts estimate future growth from the total used-space history, so uneven OSD usage can reach a threshold sooner than the forecast suggests. A threshold the fullest OSD has already reached is shown as now. If a threshold cannot be read, its count and forecast stay unknown and the table says Threshold unavailable. CCD does not read the thresholds of plain Ceph clusters, so they always show Threshold unavailable and are left out of the Nearfull and Full counts.

S3 multisite replication

Open S3 from the overview, then S3 multisite, to see the replication status of each croit cluster. CCD only reads this status with the cluster's configured credential; it never configures replication or performs a failover.

• Replication that is turned off shows as Disabled, never as a healthy primary site.
• Metadata sync and Incoming data sync are reported separately. A primary site is the metadata source but can still lag behind data written on another site.
• The number of shards behind counts replication log shards with pending changes, not objects or bytes. While a site is behind, the time shown is its Oldest pending change; once it is in sync, it is the Last confirmed time the cluster reported. All times are UTC.
• A role or write mode the cluster did not report shows Unknown; a sync status it did not report shows Status unavailable. When the status cannot be read at all, the page names the cluster it left out; check that cluster's connection, the permissions of its read-only credential and its feature licence.
• Checked at shows when CCD read the status. CCD caches it briefly and refreshes it with the dashboard, so this view does not replace real-time failover monitoring.
• Plain Ceph clusters and the demo clusters are marked as not supported here. A status that cannot be read is never shown as disabled replication.

Refreshing

Live views and navigation counts update on their own each time CCD reads the clusters again, so you do not need to reload the page. A change on a cluster can take a little while to appear.

Logs

Select servers, OSDs, services or HA groups in their table and choose Logs. The logs page opens filtered to your selection, and the filter bar names each part of it: the cluster, the host and the service. Add or remove conditions there, for example a priority or a text in the message, the same way as in croit.

To read one cluster's log, pick the cluster in the page heading, as on the other pages under Servers. The viewer then shows only that cluster's lines and drops the Cluster column.

The viewer has two modes:

• A time range. The chart above the lines shows how the matches are spread over the range, and the viewer shows the first 1,000 lines from its start. Narrow the range to see later lines. One range covers at most 24 hours.
• Tail follows new lines from every selected cluster as they are written.

When a cluster cannot be read, the viewer says so once and the other clusters keep delivering lines. A followed log catches up on that cluster from where it stopped as soon as it answers again, so no interval is skipped.

Plain Ceph clusters keep one log for the whole cluster and only its latest entries. The viewer shows all of their lines: a selection, a priority or a text condition does not narrow them, and a past time range is not available for them; use Tail instead.

On narrow screens the navigation collapses to a column of icons, and it scrolls when it is taller than the window, so its lower entries and Logout stay reachable.