> 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.0/monitor-the-weka-cluster.md).

# Monitor the Cluster

- [Deploy monitoring tools using the WEKA Management Station (WMS)](https://docs.weka.io/5.0/monitor-the-weka-cluster/deploy-monitoring-tools-using-the-weka-management-station-wms.md): Deploy the monitoring tools, LWH, and WEKAmon, using the WEKA Management Station (WMS) in an on-premises environment.
- [WEKA Home - The WEKA support cloud](https://docs.weka.io/5.0/monitor-the-weka-cluster/the-wekaio-support-cloud.md): Improve the WEKA support process with WEKA Home.
- [Local WEKA Home overview](https://docs.weka.io/5.0/monitor-the-weka-cluster/the-wekaio-support-cloud/local-weka-home-overview.md): Local WEKA Home is a private instance of WEKA Home deployed with a WEKA cluster in a private network.
- [Deploy Local WEKA Home on K8s](https://docs.weka.io/5.0/monitor-the-weka-cluster/the-wekaio-support-cloud/deploy-local-weka-home-v4.x-on-k8s.md): Manage the deployment, upgrade, and maintenance of Local WEKA Home (LWH) on Kubernetes (K8s) cluster. This deployment method provides a scalable, on-premises observability solution for WEKA clusters.
- [Deploy Local WEKA Home on K3s](https://docs.weka.io/5.0/monitor-the-weka-cluster/the-wekaio-support-cloud/local-weka-home-deployment.md): Manage the deployment, upgrade, and maintenance of Local WEKA Home (LWH) on K3s. This single-node architecture provides an on-premises observability solution for WEKA clusters.
- [Deploy Local WEKA Home on Minikube](https://docs.weka.io/5.0/monitor-the-weka-cluster/the-wekaio-support-cloud/deploy-local-weka-home-v2.x.md): Deploy, upgrade, and manage Local WEKA Home (LWH) v2.x on Minikube, an on-premises, observability solution for WEKA clusters.
- [Explore cluster insights](https://docs.weka.io/5.0/monitor-the-weka-cluster/the-wekaio-support-cloud/explore-cluster-insights-and-statistics.md)
- [Explore performance statistics in Grafana](https://docs.weka.io/5.0/monitor-the-weka-cluster/the-wekaio-support-cloud/explore-performance-statistics-in-grafana.md)
- [Manage alerts and integrations](https://docs.weka.io/5.0/monitor-the-weka-cluster/the-wekaio-support-cloud/manage-alerts-and-integrations.md)
- [Enforce security and compliance](https://docs.weka.io/5.0/monitor-the-weka-cluster/the-wekaio-support-cloud/enforce-security-and-compliance.md)
- [Optimize support and data management](https://docs.weka.io/5.0/monitor-the-weka-cluster/the-wekaio-support-cloud/optimize-support-and-data-management.md)
- [Export cluster metrics to Prometheus](https://docs.weka.io/5.0/monitor-the-weka-cluster/the-wekaio-support-cloud/export-cluster-metrics-to-prometheus.md): Export a set of WEKA cluster metrics from CWH directly into Prometheus without using WEKAmon.
- [Set up WEKAmon for external monitoring](https://docs.weka.io/5.0/monitor-the-weka-cluster/external-monitoring.md): Configure WEKAmon to integrate Grafana and Prometheus for centralized monitoring of WEKA cluster metrics, logs, alerts, and statistics.
- [Monitor WEKA clusters in Kubernetes with Prometheus and Grafana](https://docs.weka.io/5.0/monitor-the-weka-cluster/monitor-weka-clusters-in-kubernetes-with-prometheus-and-grafana.md): Deploy Prometheus and Grafana to monitor the health and performance of WEKA clusters in Kubernetes.


---

# 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.0/monitor-the-weka-cluster.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.