# Control Plane Kloudfuse Overview

The **Kloudfuse Overview** summarizes all monitored information in a series of components.

Follow these steps to get to the **Kloudfuse Overview** interface:

1. Click the **Control Plane** tab, and then the **Kloudfuse Overview** option in the drop-down menu.

2. The **Kloudfuse Overview** interface appears.
3. The **Kloudfuse Overview** interface is organized into the following sections:

- [Kloudfuse Cluster](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/kloudfuse/#cluster)
   - [Monitored Clusters](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/kloudfuse/#monitored)
   - [Stream Overview](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/kloudfuse/#stream)
   - [Agent Overview](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/kloudfuse/#agent)
   - [Service Overview](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/kloudfuse/#service)

## Using the Kloudfuse Overview

The affordances of the **Kloudfuse Overview** interfaces are:

1. Click  to add new panels to the interface.

1. **Overall interval**. The default is **Last 6 hours**. Click the drop-down to use the time picker and select the appropriate time interval.

2. **Refresh display**: click  (Refresh) to update the display.
3. Use the **orgId** selector to show data from _All_ monitored organizations, or only one of them.
4. Use the **target** selector to show data from _All_ monitored targets, or only one of them.
5. Use the **namespace** selector to show data from _All_ monitored namespaces, or only one of them.
6. The **View type** selector enables you to specify the view by selecting one of the following interfaces:
   - [Control Plane Metrics](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/metrics/)
   - [Control Plane Events](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/events/)
   - [Control Plane Logs](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/logs/)
   - [Control Plane Traces](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/traces/)
   - [Control Plane Outliers](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/outliers/)
   - [Control Plane System](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/system/)

## Kloudfuse Cluster

The **Kloudfuse Cluster** section of the interface provides key information for managing your cluster.

**Kloudfuse Cluster Installation**
This table contains information about the **Cluster Name**, the **Namespace** where the stack is deployed, the **Helm Chart Revision**, and the Kloudfuse software **Version**.

**Predicted and Current Available Space**
This table reports on storage information, in GB units. It lists the **Kube service**, and its **Remaining %** of space, **Current** usage, usage **In 1 Day**, the **Cluster** that uses the service, the **Namespace** where the cluster is deployed, and the **Organization Id**.

**Total Disk Space Usage/Stream**
This pie chart reports the proportional use of disk space storage for each type of streaming data: logs, metrics, events, traces, and so on.

Hover your pointer over each section of the chart to see more detailed information.

**Per Day Disk Used/Stream**
This pie chart reports the _daily_ use of disk space for each stream.

Hover your pointer over each section of the chart to see more detailed information.

**Aggregate Cluster Storage Usage**
This chart reports on the aggregate storage allocation for each cluster over the _lifetime_ of the cluster.

This value is independent of the time interval that you select in the [time picker](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/kloudfuse/#time-picker).

**CPU Usage (per node)**
This combined line chart represents the proportional CPU utilization by each node, during the time specified by the [time picker](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/kloudfuse/#time-picker).

**Memory Usage (per node)**
This combined line chart represents the proportional memory utilization by each node, during the time specified by the [time picker](https://docs.kloudfuse.com/platform/4.0.2/administration/control-plane/kloudfuse/#time-picker).

**Kloudfuse Nodes**
This table summarized the information for all nodes in the cluster by **Nodes** hostname, their **OS Image** (platform such as Amazon Linux 2, or Container-Optimized OS from Google, or others), the **State** of nodes (Ready), the **Core Allocatable**, **Memory Allocatable (GB)**, the **Time** of the last reading, and the **Org Id**.

**Kfuse Service**
This table reports on all the **Kfuse Services** deployed as part of the Kloudfuse cluster installation, the **Actual Pod Count**, the **Desired/Expected Pod Count**, and the **Time** of the last reading.

**Service Status**
A singular response on the state of services: _OK_ or _Degraded_.

**Pods in Failed State**
This table lists all pods that failed: the **Time** of the last reading, the **Kube Namespace**, the **Value**, and **Pod Name**.

## Monitored Clusters

The Monitored Clusters section reports on the clusters, the **Agent Version**, and the **Monitored Host Count**.

## Stream Overview

The **Stream Overview** section reports on the activities of the various streams, such as _Metrics_, _Events_, _Logs_, _Traces_, and _RUM_.

For each stream type, Kloudfuse displays the following line charts:

- Total space consumed
- Incoming size per sample
- Space per sample
- Samples per second
- Samples per source/sec

## Agent Overview

The **Agent Overview** section reports on the workload of agents for each stream type.

Kloudfuse displays the following line charts:

- Sent metric points per second
- Sent logs per second
- Sent spans per second

## Service Overview

The **Service Overview** section reports on the performance of various internal Kloudfuse services, by metric type: metrics, events, logs, and traces.

Kloudfuse displays the following line charts:

- Ingester HTTP latency for each metric type
- Kafka consumer lag
- Pinot table ingestion rate
- Query throughput by service
- Query service API latency
- Pinot Broker query execution
- Query service error count
- Ingester HTTP error count
- Rows dropped due to cardinality limit
- Pinot tables state