> For the complete documentation index, see [llms.txt](https://docs.eventoframework.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventoframework.com/evento-gui/cluster-status-experimental.md).

# Cluster Status (Experimental)

The Cluster Status page provides a comprehensive overview of the health and status of your Evento cluster. It consists of two primary sections: Bundle Instances and Consumers.

#### Bundle Instances

The Bundle Instances section displays all connected bundles within your cluster. Each bundle is represented by a card containing essential information:

* **Bundle Name:** The unique identifier of the bundle.
* **Status:** The current status of the bundle (e.g., Available, Unavailable).
* **Replica Count:** The number of instances running for the bundle.
* **Instance IDs:** A list of the unique identifiers for each bundle instance.

{% hint style="info" %}
**Changed in Evento v2.** The Spawn Instance / Kill Instance actions were removed. Evento Server no longer starts or stops bundle processes — that is owned by your orchestrator (e.g. Kubernetes or Nomad). This page is now a read-only view of the instances currently connected to the cluster.
{% endhint %}

By monitoring the Bundle Instances section, you can see which bundle instances are currently connected and confirm your cluster has the capacity it needs to handle the workload.

<figure><img src="https://3512123521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTdWWm782uxBjp7snBdDU%2Fuploads%2Fgit-blob-96a799f5eb723c91ebcd73ec7eeff4cac83f0273%2Fimage.png?alt=media" alt=""><figcaption><p>Bundle Instances</p></figcaption></figure>

#### Consumers

The Consumers section provides a list of all active consumers within your cluster. For each consumer, the following information is displayed:

* **Consumer Name (Identifier):** The Consumer Identifier composed by the {{Component Name}} - {{Component Version}} ({{Context}})
* **Bundle**
* **Shared Instances:** A list of bundle instances with which the consumer is shared.

<figure><img src="https://3512123521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTdWWm782uxBjp7snBdDU%2Fuploads%2Fgit-blob-9f74d5ae98e1dd45aac567e36a41ad663533daa5%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

**By clicking on a specific consumer, you can access additional details, such as:**

* **Last Consumed Event Identifier:** The identifier of the last event processed by the consumer.
* **Dead Event Queue:** A list of events that failed to be processed. From here you can re-enqueue events for reprocessing or delete them — this is the only mutating action left in the GUI's otherwise read-only surface.
* **Parallel:** shown only for consumers that dispatch handlers to a [consumer executor](/evento-framework/eventobundle/parallel-consumers.md) — the executor names the consumer depends on, how many handler tasks are in flight, how often a cycle ended early because the executor was saturated, and how many transient failures its parallel handlers hit. A climbing *Saturated* count means the executor is the bottleneck.

<figure><img src="https://3512123521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTdWWm782uxBjp7snBdDU%2Fuploads%2Fgit-blob-beca70a2979bae52999c68468fde58a6ee8d6570%2Fimage.png?alt=media" alt=""><figcaption><p>Consumer Detailed Status</p></figcaption></figure>

The Cluster Status page, with its Bundle Instances and Consumers sections, offers a valuable tool for managing and monitoring your Evento cluster. By effectively utilizing this information, you can optimize performance, troubleshoot issues, and ensure the overall health of your system.

{% hint style="info" %}
Consumers register (and re-register) automatically every time a bundle establishes a session with the server. If the list is empty, make sure both the server and the bundles run Evento **2.3.1 or later** — earlier 2.x servers silently dropped consumer registrations.
{% endhint %}
