> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/operation-guide/insights.md).

# Insights

Analyze CPU, RPC, drive load, and latency insights to identify performance bottlenecks.

Insights provide the top processes usage, remote procedure calls (RPCs), and drives load and latency. The insights help you make informed decisions about future actions to resolve bottlenecks and improve performance. The system collects insights data from the CPUs and drives.

To display insights, select **Investigate > Insights**.

## CPU insights

CPU insights provide a quick usage overview of the Compute, Drives, Frontend, and Gateway processes, which run on stateless clients or backends.

CPU insights show the average load in the last 15 minutes and the top 10 processes with the highest CPU usage every minute.

You can select up to three processes to show the top three RPCs that kept the process busy. You can compare the RPCs between the selected processes.

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-958bdae9d4339c7eb73f3e943ad18c3336d67edd%2Fcompute_cores_insights.png?alt=media" alt=""><figcaption><p>Top RPC calls of the compute cores</p></figcaption></figure></div>

### Display the top RPC calls of the compute cores

1. Select **COMPUTE (CPU)**.
2. Select the compute cores you want to compare (maximum three).

### Display the top RPC calls of the drive cores

1. Select **DRIVES (CPU)**.
2. Select the drive cores you want to compare (maximum three).

### Display the top RPC calls of the frontend cores

1. Select **FRONTEND (CPU)**.
2. Select the frontend cores you want to compare (maximum three).

### Display the top RPC calls of the protocol gateways

1. Select **GATEWAY (CPU)**.
2. Select the gateway cores you want to compare (maximum three).

## Drive insights

Drives insight provides a load overview of the drives in the cluster. The view of the drives is divided into three groups based on the load level. It shows the drives information when reaching a medium (load level between 128 and 254) and high load (load level 255).

You can compare each drive's latency with the average and other drives.

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-e59584ff13d9da4215a4dc2a0b82b223d628585a%2Finsights_NVMe.png?alt=media" alt=""><figcaption><p>Top drives' latency</p></figcaption></figure></div>

### Display the top drives' latency

1. Select **NVMe**.
2. Select the backend drives you want to compare (maximum three).


---

# 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.weka.io/operation-guide/insights.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.