> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/summary.md).

# Summary

<div data-with-frame="true"><figure><img src="/files/hz4dRyDO9GpFunXFeqBt" alt=""><figcaption></figcaption></figure></div>

## 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`.

<div data-with-frame="true"><figure><img src="/files/mXYmngVxMHF98CNPAEwJ" alt=""><figcaption></figcaption></figure></div>

<table><thead><tr><th width="200">Row</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Initialized</strong></td><td>Whether the node has completed initialisation.</td></tr><tr><td><strong>Active</strong></td><td>Whether the node is the active instance.</td></tr><tr><td><strong>Components</strong></td><td><code>healthy / total</code> of the participant's internal health components. Turns amber when any is unhealthy.</td></tr><tr><td><strong>Version</strong></td><td>The Canton participant version.</td></tr><tr><td><strong>UID</strong></td><td>The participant's unique identifier.</td></tr><tr><td><strong>Waiting for</strong></td><td>What the node is blocked on, when it is still initialising.</td></tr></tbody></table>

Below that, **Health components** lists each internal component with its status and description. The same table appears in more depth on the [Participant](/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/participant-and-keys.md) 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.

<div data-with-frame="true"><figure><img src="/files/r4FPV8NpVuGm3nhJQ6KY" alt=""><figcaption></figcaption></figure></div>

<table><thead><tr><th width="160">Column</th><th>Contents</th></tr></thead><tbody><tr><td><strong>Application</strong></td><td>The component name.</td></tr><tr><td><strong>CPU</strong></td><td>Current usage against the limit, as a bar and a percentage, with the raw <code>used / limit</code> beneath.</td></tr><tr><td><strong>Memory</strong></td><td>Same, in bytes.</td></tr><tr><td><strong>Restarts</strong></td><td>Container restart count. Amber when above zero.</td></tr><tr><td><strong>Since</strong></td><td>When the component last changed readiness.</td></tr><tr><td><strong>Status</strong></td><td><code>Ready</code> or <code>Pending</code>.</td></tr><tr><td>—</td><td>Grafana metrics link (participant only) and Grafana logs link.</td></tr></tbody></table>

{% hint style="info" %}
This tab uses `Pending` rather than `Degraded` for a component that is not ready — the same underlying state, a different word. The [Applications](/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/applications.md) list shows the operator's specific reason instead.
{% endhint %}

### Expanding a row

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

<div data-with-frame="true"><figure><img src="/files/8FebVbEMv7QNEDvzZTCO" alt=""><figcaption></figcaption></figure></div>

<table><thead><tr><th width="230">Field</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Deployment</strong></td><td>Name of the generated Deployment.</td></tr><tr><td><strong>Replicas</strong></td><td><code>ready / desired</code>.</td></tr><tr><td><strong>Service</strong></td><td>Name of the generated Service.</td></tr><tr><td><strong>Ingress</strong></td><td>Name of the generated IngressRoute, for externally reachable components.</td></tr><tr><td><strong>Observed Generation</strong></td><td>The generation of the resource the operator last reconciled.</td></tr><tr><td><strong>Internal URL</strong> / <strong>External URL</strong></td><td>In-cluster and public addresses.</td></tr></tbody></table>

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.

{% hint style="warning" %}
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.
{% endhint %}

## Restart notifications

While you have a validator open, the console 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.

{% hint style="info" %}
Toasts are only shown in the desktop layout. On a narrow screen you will not see restart notifications — check the **Restarts** column instead.
{% endhint %}

## 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/summary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.