# Redpanda Console Telemetry

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [streaming-full.txt](https://docs.redpanda.com/streaming-full.txt)

---
title: Redpanda Console Telemetry
latest-redpanda-tag: v26.1.9
latest-console-tag: v3.7.3
latest-operator-version: v26.1.4
# EOL = End-of-Life (support lifecycle status)
page-is-nearing-eol: "false"
page-is-past-eol: "false"
page-eol-date: March 31, 2027
latest-connect-version: 4.93.0
docname: config/analytics
page-component-name: streaming
page-version: "26.1"
page-component-version: "26.1"
page-component-title: Streaming
page-relative-src-path: config/analytics.adoc
page-edit-url: https://github.com/redpanda-data/docs/edit/main/modules/console/pages/config/analytics.adoc
description: Learn what telemetry Redpanda Console collects by default, how it is handled, and how to disable it.
page-git-created-date: "2025-08-04"
page-git-modified-date: "2025-12-04"
support-status: supported
---

<!-- Source: https://docs.redpanda.com/streaming/current/console/config/analytics.md -->

Redpanda Console collects telemetry (analytics) data for purposes including product improvements and user experience optimization. This document explains what data is collected, how it is processed, and how you can disable telemetry if desired.

## [](#what-is-tracked-by-default)What is tracked by default

When telemetry is enabled, which is the default behavior, Redpanda Console collects metadata and sends it securely to Redpanda.

### [](#redpanda-console-metadata)Redpanda Console metadata

The following information is collected from the running instance of Redpanda Console:

-   Startup timestamp (when the Redpanda Console process starts)

-   Runtime UUID (a unique ID generated per instance)

-   Redpanda Console version and build timestamp

-   License hash, license type, and license organization

-   Kafka configuration hash (anonymized)

-   Whether Kafka is connected as `localhost`

-   Behavioral user analytics


### [](#cluster-metadata)Cluster metadata

The following information is collected from the connected Kafka cluster:

-   Cluster configuration details (excluding sensitive values)

-   Broker log dir statistics such as the size

-   Topic configurations (settings only, no message contents)

-   Consumer group metadata (total count, and counts by protocol and state)

-   General cluster metadata:

    -   Number of brokers

    -   Number of topics

    -   Number of partitions

    -   Number of racks

    -   Cluster ID



## [](#how-telemetry-data-is-handled)How telemetry data is handled

Telemetry data is processed with the following features:

-   All telemetry payloads are signed and encoded as JWTs

-   Data is sent using HTTPS POST requests to Redpanda’s telemetry endpoint

-   Configuration data is anonymized using secure hashes

-   No message contents or credentials are collected or transmitted


## [](#disable-telemetry)Disable telemetry

To turn off telemetry and user tracking, set the following in your Redpanda Console configuration:

### Standalone

```yaml
analytics:
  enabled: false
```

### Kubernetes embedded

When Redpanda Console is part of the Redpanda Helm chart or Operator:
#### Operator

`redpanda-console`.yaml

```yaml
apiVersion: cluster.redpanda.com/v1alpha2
kind: Console
metadata:
  name: redpanda-console
spec:
  clusterRef:
    name: redpanda
  config:
    analytics:
      enabled: false
```

#### Helm

`redpanda-values.yaml`

```yaml
console:
  enabled: true
  console:
    config:
      analytics:
        enabled: false
```

### Kubernetes standalone

When using the standalone Redpanda Console Helm chart:

`console-values.yaml`

```yaml
config:
  analytics:
    enabled: false
```

Restart the Redpanda Console service to apply the change and stop all telemetry and user tracking.