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

# Diagnose the Local WEKA Home

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.weka.io/monitor-the-weka-cluster/the-wekaio-support-cloud/deploy-local-weka-home-on-k3s/diagnose-the-local-weka-home.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.