kapacitor record

The kapacitor record command and its subcommands record the result of an InfluxDB query or a snapshot of the live data stream.

To replay the recording, see kapacitor replay.

Usage

kapacitor record [subcommand] [flags]

Subcommands

Subcommand	Description
batch	Record a batch task
query	Record an InfluxDB query
stream	Record a stream task

Was this page helpful?

Thank you for your feedback!

Support and feedback

Thank you for being part of our community! We welcome and encourage your feedback and bug reports for Kapacitor and this documentation. To find support, use the following resources:

Edit this page Submit docs issue Submit Kapacitor issue

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.11 is now available

InfluxDB 3 Core 3.11 improves processing engine trigger reliability and adds a configurable graceful shutdown.

Key updates in InfluxDB 3 Core 3.11:

Processing engine trigger reliability improvements—capped async trigger concurrency, bounded retries for failed triggers, and WAL triggers that skip empty flushes.
Configurable graceful shutdown with the new --shutdown-timeout option.
Read the announcement
InfluxDB 3 Core release notes

InfluxDB 3 Enterprise 3.11: A significant performance upgrade for complex time series workloads

Performance and flexibility for heavier, more complex workloads.

Key updates in InfluxDB 3 Enterprise 3.11:

Upgraded storage engine reaches general availability. New clusters default to Parquet; upgrade with --upgrade-pacha-tree.
In-place and incremental backup and restore.
Integrated Explorer UI—run with --mode all,webui.
Bulk import: import from remote object store sources (for example, S3) with configurable concurrency.
Compaction and query performance improvements.
Catalog migration—back up your catalog before upgrading.
Read the announcement
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

kapacitor record

Usage

Subcommands

Related

Support and feedback

Where are you running InfluxDB?

AWS

GCP

Azure

Default

Custom