> 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/optimize-support-and-data-management.md).
# Optimize support and data management
Manage diagnostics, usage reports, data forwarding, and API access in Local WEKA Home.
## Cloud forwarding
This feature is aimed at customers who want to send events, usage, and analytics data from the Local WEKA Home to the cloud WEKA Home for supportability and monitoring by the Customer Success Team. The forwarded data is not anonymized.
**Related topic**
[Deploy Local WEKA Home on K3s](/monitor-the-weka-cluster/the-wekaio-support-cloud/deploy-local-weka-home-on-k3s.md) — see **Forward data from the Local WEKA Home to the Cloud WEKA Home**
## API Documentation
The Local WEKA Home supports a RESTful API. This is useful when automating the interaction with the Local WEKA Home and integrating it into your workflows or monitoring systems.
To access the API documentation:
1. Select the profile icon, and from the menu that appears, select User Management and create an API token.
Access the API Docs
2. Select **API Docs** and apply the API token.
A static API documentation is also found in: .
---
# 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/monitor-the-weka-cluster/the-wekaio-support-cloud/optimize-support-and-data-management.md?ask=&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.
