Documentation

Create a Last Value Cache

Use the influxdb3 create last_cache command to create a Last Value Cache (LVC). Provide the following:

  • Database (-d, --database): (Required) The name of the database to associate the LVC with. You can also use the INFLUXDB3_DATABASE_NAME environment variable to specify the database.
  • Token (--token): (Required) Your InfluxDB 3 Core

authentication token. You can also use the INFLUXDB3_AUTH_TOKEN environment variable to specify the token.

  • Table (-t, --table): (Required) The name of the table to associate the LVC with.

  • Key columns (--key-columns): Specify which columns to include in the primary key of the cache. Rows in the LVC are uniquely identified by their timestamp and key columns, so include all the columns you need to identify each row. These are typically tags, but you can use any columns with the following types:

    • String
    • Integer
    • Unsigned integer
    • Boolean
  • Value columns (--value-columns): Specify which columns to cache as value columns. These are typically fields but can also be tags. By default, time and columns other than those specified as --key-columns are cached as value columns.

  • Count (--count): The number of values to cache per unique key column combination. The supported range is [1-10]. The default count is 1.

  • Time-to-Live (TTL) (--ttl): The time-to-live for cached values in humantime form. The default TTL is four hours.

  • Cache name: A unique name for the cache. If you don’t provide one, InfluxDB automatically generates a cache name for you.

influxdb3 create last_cache \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
--table
TABLE_NAME
\
--key-columns
KEY_COLUMNS
\
--value-columns
VALUE_COLUMNS
\
--count
COUNT
\
--ttl
TTL
\
LVC_NAME

Use the HTTP API

To use the HTTP API to create a Last Value Cache, send a POST request to the /api/v3/configure/last_cache endpoint.

POST /api/v3/configure/last_cache
curl -X POST "https://localhost:8181/api/v3/configure/last_cache" \
  --header "Authorization: Bearer 
AUTH_TOKEN
"
\
--json '{ "db": "
DATABASE_NAME
",
"table": "
TABLE_NAME
",
"name": "
LVC_NAME
",
"key_columns": ["
KEY_COLUMNS
"],
"value_columns": ["
VALUE_COLUMNS
"],
"count":
COUNT
,
"ttl":
TTL
}'

Example

 curl -X POST "https://localhost:8181/api/v3/configure/last_cache" \
  --header "Authorization: Bearer 00xoXX0xXXx0000XxxxXx0Xx0xx0" \
  --json '{
    "db": "example-db",
    "table": "home",
    "name": "homeLastCache",
    "key_columns": ["room", "wall"],
    "value_columns": ["temp", "hum", "co"],
    "count": 5,
    "ttl": 14400
  }'

Response codes:

  • 201 : Success. Last cache created.
  • 400 : Bad request.
  • 401 : Unauthorized.
  • 404 : Cache not found.
  • 409 : Cache already exists.

API parameter differences

Column format: The API uses JSON arrays ([“room”, “wall”]) instead of the CLI’s comma-delimited format (room,wall). TTL format: The API uses seconds (14400) instead of the CLI’s humantime format (4h, 4 hours).

Replace the following:

  • DATABASE_NAME: the name of the database to associate the LVC with

  • AUTH_TOKEN: your InfluxDB 3 Core

    authentication token

  • TABLE_NAME: the name of the table to associate the LVC with

  • KEY_COLUMNS: a comma-delimited list of columns to use to unique identify each series–for example: room,wall

  • VALUE_COLUMNS: a comma-delimited list of columns to cache as value columns–for example: temp,hum,co

  • COUNT: the number of last values to cache per series–for example: 5

  • TTL: the TTL of cached values in humantime form–for example: 10s, 1min 30sec, 3 hours

  • LVC_NAME: a unique name for the LVC

The cache imports the distinct values from the table and starts caching them.

LVC size and persistence

The LVC is stored in memory, so it’s important to consider the size and persistence of the cache. For more information, see Important things to know about the Last Value Cache.


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.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 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 is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

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