> 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/5.1/monitor-the-weka-cluster/the-wekaio-support-cloud/local-weka-home-deployment/diagnose-the-local-weka-home.md).

# Diagnose the Local WEKA Home

Assess Local WEKA Home health on K3s and capacity with one command. homecli local diagnose is available in LWH 5.0 and later.

Unlike `homecli local status`, which confirms reachability, `homecli local diagnose` evaluates deployment health and sizing.

### Before you begin

* Use LWH 5.0 or later.
* Ensure `homecli` can access the LWH deployment.
* Use an account authorized to inspect the deployment.

### Diagnose Local WEKA Home

1. Run the following command:

```sh
homecli local diagnose
```

2. Review the report. Apply each recommended action.
3. For automated processing, output the report in JSON format:

```sh
homecli local diagnose -o json
```

### Interpret the report

The report includes:

* Pod health across all LWH components.
* Node, PVC, and disk capacity, including disk fill estimates.
* Stats and forwarding pipeline backlogs.
* NATS and FSQ queue state.
* Database and VictoriaMetrics status.
* Resource sizing recommendations based on current load and the selected resource preset.

When the command detects a problem, it raises a targeted alert. A `[MIGRATION STUCK]` banner includes the command required to resolve it.

Run the command in the following situations:

* After a new deployment, to confirm the installation is healthy and correctly sized.
* Before and after an upgrade, to validate resource preset recommendations.
* When investigating performance issues, backlogs, or disk space alerts.

The LWH deployment diagnostics archive automatically bundles a `homecli local diagnose -o json` snapshot, so a separate run before contacting support is not required.


---

# 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/5.1/monitor-the-weka-cluster/the-wekaio-support-cloud/local-weka-home-deployment/diagnose-the-local-weka-home.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.