---
title: Usage telemetry
description: InfluxData collects telemetry data to help improve the InfluxDB 3 Core. Learn what data InfluxDB 3 Core collects and sends to InfluxData, how it’s used, and how you can opt out.
url: https://docs.influxdata.com/influxdb3/core/reference/telemetry/
estimated_tokens: 1236
product: InfluxDB 3 Core
version: core
---

# Usage telemetry

InfluxData collects information, or *telemetry data*, about the usage of InfluxDB 3 Core to help improve the product. Learn what data InfluxDB 3 Core collects and sends to InfluxData, how it’s used, and how you can opt out.

## What data is collected

InfluxDB 3 Core collects the following telemetry data:

### System metrics

-   **CPU utilization**: Process-specific CPU usage
-   **Memory usage**: Process memory consumption in MB
-   **Cores**: Number of CPU cores in use
-   **OS**: Operating system information
-   **Version**: InfluxDB 3 Core version
-   **Uptime**: Server uptime in seconds

### Write metrics

-   **Write requests**: Number of write operations
-   **Write lines**: Number of lines written
-   **Write bytes**: Amount of data written in MB

### Query metrics

-   **Query requests**: Number of query operations

### Storage metrics

-   **Parquet file count**: Number of Parquet files
-   **Parquet file size**: Total size of Parquet files in MB
-   **Parquet row count**: Total number of rows in Parquet files

### Processing engine metrics

-   **WAL triggers**: Write-Ahead Log trigger counts
-   **Schedule triggers**: Scheduled processing trigger counts
-   **Request triggers**: Request-based processing trigger counts

### Instance information

-   **Instance ID**: Unique identifier for the server instance
    
-   **Cluster UUID**: Unique identifier for the cluster
    
-   **Storage type**: Type of object storage being used
    
-   **Invocation**: How the server was started
    
-   **Product type**: “Core”
    

## Collection frequency

-   **System metrics** (CPU, memory): Collected every 60 seconds
-   **Write and query metrics**: Collected per operation, rolled up every 60 seconds
-   **Storage and processing engine metrics**: Collected at snapshot time (when available)
-   **Instance information**: Static data collected once

Telemetry data is transmitted once per hour.

## Disable telemetry

To “opt-out” of collecting and sending InfluxDB 3 Core telemetry data, include the `--disable-telemetry-upload` flag or set the `INFLUXDB3_TELEMETRY_DISABLE_UPLOAD` environment variable when starting InfluxDB 3 Core.

**Default:** `false`

| influxdb3 flag | Environment variable |
| --- | --- |
| --disable-telemetry-upload | INFLUXDB3_TELEMETRY_DISABLE_UPLOAD |

#### Command line flag

```sh
influxdb3 serve --disable-telemetry-upload
```

#### Environment variable

```sh
export INFLUXDB3_TELEMETRY_DISABLE_UPLOAD=true
```

When telemetry is disabled, no usage data is collected or transmitted.

## Data handling

The telemetry data is used by InfluxData to understand product usage patterns, improve product performance and reliability, prioritize feature development, and identify/resolve issues. No personally identifiable information (PII) is collected.

## Privacy and security

All telemetry data is transmitted securely via HTTPS. No database contents, queries, or user data is collected; only operational metrics and system information is transmitted.

All data collection follows InfluxData’s privacy policy.

[telemetry](/influxdb3/core/tags/telemetry/) [monitoring](/influxdb3/core/tags/monitoring/) [metrics](/influxdb3/core/tags/metrics/) [observability](/influxdb3/core/tags/observability/)
