Summary

The Summary tab is where you start when a validator is not behaving. It shows the participant node's health and then every component the validator owns, in one table.

Metric cards

Card	Value
Status	Ready or Degraded, with a badge showing the percentage of components that are ready
Network	DevNet, TestNet, or MainNet
Balance	Canton Coin balance, to two decimal places

Participant

Shown once the participant has reported status. The badge is Connected, Disconnected, or Initializing.

Row	Meaning
Initialized	Whether the node has completed initialisation.
Active	Whether the node is the active instance.
Components	healthy / total of the participant's internal health components. Turns amber when any is unhealthy.
Version	The Canton participant version.
UID	The participant's unique identifier.
Waiting for	What the node is blocked on, when it is still initialising.

Below that, Health components lists each internal component with its status and description. The same table appears in more depth on the Participant tab.

Applications

One row per component, always in this order:

Participant · Validator Backend · Wallet UI · CNS UI · PQS · Wallet Gateway

PQS and Wallet Gateway rows only appear when those components are enabled.

Column	Contents
Application	The component name.
CPU	Current usage against the limit, as a bar and a percentage, with the raw used / limit beneath.
Memory	Same, in bytes.
Restarts	Container restart count. Amber when above zero.
Since	When the component last changed readiness.
Status	Ready or Pending.
—	Grafana metrics link (participant only) and Grafana logs link.

This tab uses Pending rather than Degraded for a component that is not ready — the same underlying state, a different word. The Applications list shows the operator's specific reason instead.

Expanding a row

Each row expands to show what the operator created and what Kubernetes reports back:

Field	Meaning
Deployment	Name of the generated Deployment.
Replicas	ready / desired.
Service	Name of the generated Service.
Ingress	Name of the generated IngressRoute, for externally reachable components.
Observed Generation	The generation of the resource the operator last reconciled.
Internal URL / External URL	In-cluster and public addresses.

Then Resources by replica, a per-pod table of phase, restarts, and CPU and memory usage against requests and limits; and finally the component's Kubernetes conditions, with type, status, reason, message, and last transition time.

If live usage figures are missing and a note says the cluster metrics API is not reachable, the metrics-server component is not installed or not healthy in your cluster. Requests and limits still display; only actual usage is unavailable.

Restart notifications

While you have a validator open, the UI watches container restart counts. If a component restarts, a toast appears naming it and the number of new restarts. This is the fastest way to notice a crash-looping component without watching the table.

Toasts are only shown in the desktop layout. On a narrow screen you will not see restart notifications — check the Restarts column instead.

Empty state

No application status — The validator has not reported any application status yet. Normal for the first few seconds after applying a Validator; persistent otherwise, check the operator logs.