Documentation

kapacitor record query

The kapacitor record query command records the result of an InfluxQL query. Once the recording is stopped, the command outputs the recording ID. If no recording ID is specified, Kapacitor assigns a random ID.

The command requires the following:

  • InfluxQL query: Use the -query flag
  • Recording type: Use the -type flag and pass either batch or query

To replay the recording, see kapacitor replay.

Usage

kapacitor record query [flags]

Flags

FlagDescription
-queryRequired: Query to record.
-typeRequired: Recording type (stream or batch)
-clusterNamed InfluxDB cluster or instance to query
-no-waitRun recording in the background
-recording-idID to assign to the recording

Examples

Record an InfluxQL query

influx record query \
  -query "SELECT temp, hum FROM db.rp.home" \
  -type batch

Record an InfluxQL query and assign a custom recording ID

influx record query \
  -query "SELECT temp, hum FROM db.rp.home" \
  -type batch \
  -recording-id example-query-rec

Record an InfluxQL query for a specific InfluxDB cluster

influx record query \
  -query "SELECT temp, hum FROM db.rp.home" \
  -type batch \
  -cluster influxdb-enterprise

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:

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