Documentation

Kapacitor

kapacitor record stream

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

  • Recording duration: Use the -duration flag
  • Task ID: Use the -task flag

To replay the recording, see kapacitor replay.

Usage

kapacitor record stream [flags]

Flags

FlagDescription
-durationRequired: How long to record the data stream
-no-waitRun recording in the background
-recording-idID to assign to the recording
-taskRequired: Task ID (uses the dbrp value in the task)

Examples

Record a stream task

kapacitor record stream \
  -task example-task-id \
  -duration 1h

Record a stream task and assign a custom recording ID

kapacitor record stream \
  -task example-task-id \
  -duration 1h \
  -recording-id 1h-example-stream-rec

Was this page helpful?

Thank you for your feedback!

© 2025 InfluxData, Inc.

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

  • InfluxDB Cloud
  • InfluxDB OSS or Enterprise
AWS

  • US West (Oregon)

GCP
Azure
Default
Custom

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

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