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

  • 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 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!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 2026, 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