Documentation

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

  • 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 flagEnvironment variable
--disable-telemetry-uploadINFLUXDB3_TELEMETRY_DISABLE_UPLOAD

Command line flag

influxdb3 serve --disable-telemetry-upload

Environment variable

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.


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2