> 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/applications.md).

# Applications

### Applications Overview

Each application deployed across managed validators is displayed as a row with some key details and indicators.

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

Each application is displayed as a row with the following columns:

| Column        | Description                                                             |
| ------------- | ----------------------------------------------------------------------- |
| **Name**      | The name of the application.                                            |
| **Type**      | The application type (`ui` or `backend`).                               |
| **Validator** | The validator which has the application installed.                      |
| **Status**    | Current readiness status of the application.                            |
| **Replicas**  | The number of running replicas out of the desired count (e.g. `1 / 1`). |

{% hint style="info" %}
At the top of the application table, a summary bar shows aggregate counts for the current validator selection:

* total: total number of applications installed.
* ready: number of applications with a Ready status.
* issues: number of applications with a non-Ready status requiring attention.
  {% endhint %}

{% hint style="info" %}
\[TODO: document status values and what they indicate — e.g. In Progress, Failing, or any other states visible in production environments]
{% endhint %}

Click the **>** arrow at the right of any row, or click the row itself, to open the **application details** view.

### Application Details

Clicking on any application from the Applications list opens the **application detail view**.

The application detail view shows the runtime status, endpoints, conditions, and environment variables for the Canton application.

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

#### Status Cards

Four summary cards are shown at the top of the page:

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

| Card         | Description                                                             |
| ------------ | ----------------------------------------------------------------------- |
| **Status**   | The current readiness status of the application (e.g. `Ready`).         |
| **Replicas** | The number of running replicas out of the desired count (e.g. `1 / 1`). |
| **Type**     | The application type (`ui` or `backend`).                               |
| **Port**     | The port the application is listening on.                               |

***

#### Endpoints

The **Endpoints** section lists the network endpoints exposed by this application:

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

| Field        | Description                                                       |
| ------------ | ----------------------------------------------------------------- |
| **Internal** | The internal Kubernetes service URL for this application.         |
| **External** | The publicly accessible URL for this application (if applicable). |

Copy and external link icons are available next to each URL.

***

#### Conditions

The **Conditions** section lists the Kubernetes conditions reported for this application:

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

| Column              | Description                                                        |
| ------------------- | ------------------------------------------------------------------ |
| **Type**            | The condition type (e.g. `Ready`).                                 |
| **Status**          | Whether the condition is currently true or false.                  |
| **Reason**          | A machine-readable reason code (e.g. `DeploymentAvailable`).       |
| **Message**         | A human-readable description of the current state.                 |
| **Last transition** | The timestamp of the most recent status change for this condition. |

***

#### Environment Variables

The **Environment variables** section lists all environment variables configured for this application. A **Copy all** button in the top-right copies all variables to the clipboard.

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

| Column    | Description                                                       |
| --------- | ----------------------------------------------------------------- |
| **Name**  | The environment variable name (e.g. `SPLICE_APP_UI_AMULET_NAME`). |
| **Value** | The configured value for that variable (e.g. `Canton Coin`).      |

{% hint style="info" %}
\[TODO: document whether environment variables can be edited through the console or are read-only, and how they are managed]
{% endhint %}


---

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

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

The question should be specific, self-contained, and written in natural language.
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.