Documentation

Show information about Distinct Value Caches

Use the influxdb3 show system table command to query and output Distinct Value Cache information from the distinct_caches system table.

influxdb3 show system \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
table distinct_caches

This returns a table similar to the following:

tablenamecolumn_idscolumn_namesmax_cardinalitymax_age_seconds
wind_datawind_distinct[0, 1, 2][country, county, city]10000086400
weatherweather_distinct[0][location]100604800
bitcoinbitcoin_dis[0, 1][code, crypto]500086400
homehome_distinct[0, 1][room, wall]1200015770000

Query specific columns from the distinct_caches system table

Use the --select option to query specific columns from the distinct_caches system table. Provide a comma-delimited list of columns to return:

influxdb3 show system \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
table distinct_caches \ --select name,column_names,max_age_seconds

Sort distinct_caches system table output

Use the --order-by option to sort data from the distinct_caches system table by specific columns. Provide a comma-delimited list of columns to sort by:

influxdb3 show system \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
table distinct_caches \ --order-by max_cardinality,max_age_seconds

Results are sorted in ascending order based on the provided columns.

In the examples above, replace the following:

  • DATABASE_NAME: the name of the database to query system data from

  • AUTH_TOKEN: your InfluxDB 3 Enterprise admin

    authentication token

Use the HTTP API

To use the HTTP API to query and output cache information from the system table, send a GET or POST request to the /api/v3/query_sql endpoint.

GET /api/v3/query_sql
POST /api/v3/query_sql

Query all caches

curl -X POST "https://localhost:8181/api/v3/query_sql" \
  --header "Authorization: Bearer 
AUTH_TOKEN
"
\
--json '{ "db": "
DATABASE_NAME
",
"q": "SELECT * FROM system.distinct_caches", "format": "json" }'

Query specific cache details

curl -X POST "https://localhost:8181/api/v3/query_sql" \
  --header "Authorization: Bearer 
AUTH_TOKEN
"
\
--json '{ "db": "
DATABASE_NAME
",
"q": "SELECT * FROM system.distinct_caches WHERE name = '\''
CACHE_NAME
'
\''",
"format": "json" }'

Was this page helpful?

Thank you for your feedback!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

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

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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