> 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/4.1/support/the-wekaio-support-cloud/download-the-usage-report-or-analytics.md).

# Download the Usage Report or Analytics

## Download the Usage Report or Analytics

The Local Weka Home lets you download JSON-formatted reports to your local workstation, view them, and forward them to the Customer Success Team for case resolution and adding them to the Cloud Weka Home for offline monitoring purposes.

**Procedure:**

1. In the Local Weka Home portal, select the cluster.
2. Select the **Usage Report** or **Analytics** download button.

<figure><img src="https://1916840177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTUYL9RLgSDAkF2U90csR%2Fuploads%2FsISmE42ttS5lGJr1FFbj%2Fwmng_lwh_download_reports.png?alt=media&amp;token=4b457636-a63b-4533-a937-bd188eb0dbc9" alt=""><figcaption><p>Download the Usage Report or Analytics</p></figcaption></figure>

## Download the Usage Report or Analytics without sensitive data

Suppose you need to download the Usage Report or Analytics files to send them to the Customer Success Team (or any third party), but the data might include sensitive values you do not want to expose. For this purpose, the Local Weka Home portal allows anonymizing the data in the downloaded files.

With anonymization, **sensitive** values are affected as follows:

* The cluster name is renamed to `weka-[first part of cluster GUID]`
* Other sensitive values are removed

<details>

<summary>Usage Report default anonymized data</summary>

The following properties are affected by anonymization:

* name
* alerts
* status/name
* status/cloud

</details>

<details>

<summary>Analytics default anonymized data</summary>

The following properties are affected by anonymization:

* cluster/name
* For all hosts:
  * host/hosts/ips
  * host/hosts/host\_ip
  * host/hosts/hostname
  * host/hosts/instance\_region
  * host/hosts/aws\_instance\_region
* misc/kms/type
* misc/cloud/url
* nfs/interface\_groups/name
* nfs/interface\_groups/gateway
* nfs/interface\_groups/subnet\_mask
* s3/domain
* s3/filesystem
* smb/smb\_trusted\_domains

</details>

{% hint style="info" %}
**Note:** The anonymization option is supported with WEKA clusters of version 3.14.2 and above.
{% endhint %}

**Procedure:**

1. In the Local Weka Home portal, select the cluster.
2. Below the Usage Report and Analytics download buttons, switch on the **Enable Anonymization** option.
3. Select the **Usage Report** or **Analytics** download button.

<figure><img src="https://1916840177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTUYL9RLgSDAkF2U90csR%2Fuploads%2FANDW5KafbysFJML0F28x%2Fwmng_lwh_anonymization.png?alt=media&amp;token=8818de5f-3e2e-496a-bd15-31d5a996a542" alt=""><figcaption><p>Enable anonymization in Usage Report and Analytics</p></figcaption></figure>


---

# 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/4.1/support/the-wekaio-support-cloud/download-the-usage-report-or-analytics.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.