Documentation

Manage Distinct Value Caches with InfluxDB 3 Explorer

Use InfluxDB 3 Explorer to manage Distinct Value Caches (DVCs) in an InfluxDB 3 instance or cluster. To navigate to the Distinct Value Cache management page:

  1. In the left navigation bar, select Configure > Caches.
  2. Select the Distinct Value Caches tab.

View Distinct Value Caches

To view DVCs associated with a database, navigate to the Distinct Value Cache management page and select the database from the Select Database dropdown menu. The page lists all DVCs associated with the selected database.

Create a Distinct Value Cache

On the Distinct Value Cache management page:

  1. Click + Create Cache.

  2. Provide the following:

    • Cache name: A unique name for the cache.

    • Database: The database the cache is associated with.

    • Table: The target table for the cache. As data is written to the table, it populates the cache. You must select a database before you can select a table.

    • Column names: Select columns to cache distinct values from. These are typically InfluxDB tags, but you can also use fields. combinations to cache. Once this limit is exceeded, InfluxDB drops the oldest cached distinct values.

    • Max Age: Specify the maximum age of cached values as a duration in humantime form. The default is 24h.

      Higher cardinality (more distinct values) in a DVC increases memory usage.

  3. Click Create.

Query a Distinct Value Cache

Use the Data Explorer to query a DVC:

  1. In the left navigation, select Query Data > Data Explorer.
  2. Select the database you want to query from the Select database dropdown menu.
  3. Click the icon next to the table associated with the DVC you want to query to expand the table. Tables with DVCs have a DVC badge below the icon.
  4. Under the Caches section of the expanded table, DVCs are identified by the DVC badge. Click the name of the DVC to generate a SQL query that queries everything from the DVC. You can also expand the DVC and select specific columns to query.
  5. Click Run Query to execute the query and return results from the cache.

Delete a Distinct Value Cache

On the Distinct Value Cache management page:

  1. Select the database associated with the cache you want to delete from the Select Database dropdown menu.
  2. In the Active Caches table, click the icon next to the cache you want to delete.

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