---
title: "Grafana Alloy data collection | Grafana Cloud documentation"
description: "Grafana Alloy data collection"
---

# Grafana Alloy data collection

Grafana Alloy includes a system that optionally and anonymously reports non-sensitive, non-personally identifiable information about Alloy to a remote statistics server. Alloy maintainers use this anonymous information to learn how the open source community runs Alloy. This data helps the Alloy team prioritize features and improve documentation.

Alloy reports anonymous usage statistics by default. To opt out, use the [CLI flag](/docs/grafana-cloud/send-data/alloy/reference/cli/run) `--disable-reporting`.

## The statistics server

Alloy sends usage statistics to a server that Grafana Labs runs. It sends data to `https://stats.grafana.org/alloy-usage-report` with an HTTP POST request. This endpoint only accepts data and isn’t available to view in a browser.

## What Alloy collects

Alloy collects the following information:

- A randomly generated anonymous UUID.
- The timestamp when Alloy first created the UUID.
- The scheduled report interval, which defaults to four hours.
- The version of Alloy.
- The operating system where Alloy runs.
- The system architecture where Alloy runs.
- A list of enabled [components](/docs/grafana-cloud/send-data/alloy/get-started/components).
- The deployment method, such as `docker`, `helm`, `operator`, `deb`, `rpm`, `brew`, or `binary`.

> Note
> 
> Alloy maintainers update this list of tracked information over time and report any changes in the CHANGELOG.

## Disable anonymous usage statistics

If possible, keep this feature enabled. It helps Grafana Labs understand how the open source community uses Alloy. To opt out of anonymous usage statistics, use the [CLI flag](/docs/grafana-cloud/send-data/alloy/reference/cli/run) `--disable-reporting` with the method that matches your install type.

### Linux

1. Edit the environment file for the service:
   
   - Debian-based systems: edit `/etc/default/alloy`
   - RedHat or SUSE-based systems: edit `/etc/sysconfig/alloy`
2. Add `--disable-reporting` to the `CUSTOM_ARGS` environment variable.
3. Restart the Alloy service:
   
   shell ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy
   
   ```shell
   sudo systemctl restart alloy
   ```

### Windows

Alloy runs as a Windows service and reads its command-line arguments from the registry.

1. Open the Registry Editor:
   
   1. Right-click the **Start** menu and select **Run**.
   2. Type `regedit` and click **OK**.
2. Navigate to `HKEY_LOCAL_MACHINE\SOFTWARE\GrafanaLabs\Alloy`.
3. Double-click the **Arguments** value.
4. Add `--disable-reporting` on a separate line at the end of the arguments list.
5. Click **OK**.
6. Restart the Alloy service:
   
   1. Right-click the **Start** menu and select **Run**.
   2. Type `services.msc` and click **OK**.
   3. Right-click the **Alloy** service and select **All Tasks > Restart**.

### macOS

Alloy reads extra command-line flags from a dedicated file when you install it with Homebrew.

1. Edit `$(brew --prefix)/etc/alloy/extra-args.txt`.
2. Add `--disable-reporting` on a separate line.
3. Restart the Alloy service:
   
   shell ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy
   
   ```shell
   brew services restart grafana/grafana/alloy
   ```

### Docker

Add `--disable-reporting` to the `alloy run` arguments in your `docker run` command:

shell ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```shell
docker run \
  -v <CONFIG_FILE_PATH>:/etc/alloy/config.alloy \
  -p 12345:12345 \
  grafana/alloy:latest \
    run --server.http.listen-addr=0.0.0.0:12345 \
    --storage.path=/var/lib/alloy/data \
    --disable-reporting \
    /etc/alloy/config.alloy
```

Replace the following:

- *`<CONFIG_FILE_PATH>`* : The path to your configuration file on the host system.

### Helm

The Grafana Alloy Helm chart includes a dedicated value to disable usage statistics. Set `alloy.enableReporting` to `false` in your `values.yaml`:

YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```yaml
alloy:
  enableReporting: false
```

Then apply the change:

shell ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```shell
helm upgrade --namespace <NAMESPACE> <RELEASE_NAME> grafana/alloy -f <VALUES_PATH>
```

Replace the following:

- *`<NAMESPACE>`* : The namespace for your Alloy installation.
- *`<RELEASE_NAME>`* : The name of your Alloy Helm release.
- *`<VALUES_PATH>`* : The path to your `values.yaml` file.

### Ansible

Set `CUSTOM_ARGS` in your playbook using the Grafana Ansible collection:

YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```yaml
- name: Install Alloy
  hosts: all
  become: true
  tasks:
    - name: Install Alloy
      ansible.builtin.include_role:
        name: grafana.grafana.alloy
      vars:
        alloy_env_file_vars:
          CUSTOM_ARGS: "--disable-reporting"
```

### Binary

Add `--disable-reporting` to the `alloy run` command:

shell ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```shell
<BINARY_PATH> run --disable-reporting <CONFIG_PATH>
```

Replace the following:

- *`<BINARY_PATH>`* : The path to the Alloy binary.
- *`<CONFIG_PATH>`* : The path to your Alloy configuration file.