Documentation

Show information about Last Value Caches

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

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

This returns a table similar to the following:

tablenamekey_column_idskey_column_namesvalue_column_idsvalue_column_namescountttl
weatherweather_last[0][location][2, 3, 4, 5, 1][precip, temp_avg, temp_max, temp_min, wind_avg]186400
bitcoinbitcoin_last[0, 1][code, crypto][4][price]114400
numbersnumbers_last[][][0, 1][a, b]514400
homehome_last[0][room][1, 2, 3][temp, hum, co]560

Query specific columns from the last_caches system table

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

influxdb3 show system \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
table last_caches \ --select name,key_column_names,value_column_names

Sort last_caches system table output

Use the --order-by option to sort data from the last_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 last_caches \ --order-by table,ttl

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 Core

    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 last value caches

curl -X POST "https://localhost:8181/api/v3/query_sql" \
  --header "Authorization: Bearer 
AUTH_TOKEN
"
\
--json '{ "db": "
DATABASE_NAME
",
"q": "SELECT * FROM system.last_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.last_caches WHERE name = '\''
CACHE_NAME
'
\''",
"format": "json" }'

Was this page helpful?

Thank you for your feedback!


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:

New in InfluxDB 3.8

Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

See the Blog Post

InfluxDB 3.8 is now available for both Core and Enterprise, alongside the 1.6 release of the InfluxDB 3 Explorer UI. This release is focused on operational maturity and making InfluxDB easier to deploy, manage, and run reliably in production.

For more information, check out:

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