Documentation

kapacitor record batch

The kapacitor record batch command records the result of a Kapacitor batch task. 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:

  • Time range to query: Use the -past flag or -start and -stop flags
  • Task ID: Use the -task flag

To replay the recording, see kapacitor replay.

Usage

kapacitor record batch [flags]

Flags

FlagDescription
-no-waitRun recording in the background
-pastSet start time via now - past
-recording-idID to assign to the recording
-startStart time for the set of queries
-stopStop time for the set of queries (default is now)
-taskRequired: Task ID (uses the queries in the task)

Examples

Record a batch task using an absolute time range

kapacitor record batch \
  -task example-task-id \
  -start 2023-01-01T00:00:00Z \
  -stop 2023-06-01T00:00:00Z

Record a batch task using a relative time range

kapacitor record batch \
  -task example-task-id \
  -past 90d

Record a batch task and assign a custom recording ID

kapacitor record batch \
  -task example-task-id \
  -past 90d \
  -recording-id 90d-example-task-rec

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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