> 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/user-guide-canton/dashboard.md).

# Dashboard

Fleet-wide validator and application health.

The Dashboard is the CatalyX UI's landing page. It answers one question — *is anything wrong?* — and gives you the Canton console.

<div data-with-frame="true"><figure><img src="https://2680825251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUGPGTcyMu8FXsdY8XQY%2Fuploads%2Fgit-blob-843402cb0fb6628bc946a92e4f489929ad61b149%2Fimage%20(150).png?alt=media" alt=""><figcaption></figcaption></figure></div>

## Summary cards

Four cards across the top aggregate every validator the UI can see.

<table><thead><tr><th width="180">Card</th><th width="230">Value</th><th>Badge</th></tr></thead><tbody><tr><td><strong>Validators</strong></td><td>Total number of validators.</td><td><strong>View all →</strong> links to the Validators list.</td></tr><tr><td><strong>Ready</strong></td><td><code>ready / total</code>.</td><td><strong>All healthy</strong> when every validator is ready.</td></tr><tr><td><strong>Issues</strong></td><td>Number of validators that are not ready.</td><td><strong>Degraded</strong> when the count is above zero.</td></tr><tr><td><strong>Applications</strong></td><td><code>ready / total</code> across every component of every validator.</td><td><strong>View all →</strong> links to the Applications list.</td></tr></tbody></table>

A validator counts as ready when its `Ready` condition is `True`. **Issues** is simply the remainder.

{% hint style="info" %}
The Applications count comes from each validator's reported component status, so it includes components that have not yet produced a workload. The [Applications](/catalyx-blockchain-manager/canton-network/version-2.0/user-guide-canton/applications.md) list is the authoritative view of what is actually deployed.
{% endhint %}

## Canton Console panel

Below the cards sits the [Canton Console](/catalyx-blockchain-manager/canton-network/version-2.0/user-guide-canton/canton-console.md) — an interactive Canton console session in the browser. It is collapsed by default and this is the only place in the UI where it appears.

## Where to go next

The Dashboard deliberately does not try to tell you *what* is wrong. When the **Issues** card is non-zero:

{% stepper %}
{% step %}
**Open the Validators list**

The [Validators list](/catalyx-blockchain-manager/canton-network/version-2.0/user-guide-canton/validators-list.md) shows per-validator status, plus the participant connection state, which is usually the fastest signal.
{% endstep %}

{% step %}
**Open the affected validator**

Its [Summary](/catalyx-blockchain-manager/canton-network/version-2.0/user-guide-canton/validators/summary.md) tab breaks readiness down per component.
{% endstep %}

{% step %}
**Read the conditions**

The [Status](/catalyx-blockchain-manager/canton-network/version-2.0/user-guide-canton/validators/status-and-specification.md) tab shows the reason and message the operator posted, which names the specific problem.
{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/user-guide-canton/dashboard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.