Documentation

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!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Read more

InfluxDB v3 enhancements and InfluxDB Clustered is now generally available

New capabilities, including faster query performance and management tooling advance the InfluxDB v3 product line. InfluxDB Clustered is now generally available.

InfluxDB v3 performance and features

The InfluxDB v3 product line has seen significant enhancements in query performance and has made new management tooling available. These enhancements include an operational dashboard to monitor the health of your InfluxDB cluster, single sign-on (SSO) support in InfluxDB Cloud Dedicated, and new management APIs for tokens and databases.

Learn about the new v3 enhancements


InfluxDB Clustered general availability

InfluxDB Clustered is now generally available and gives you the power of InfluxDB v3 in your self-managed stack.

Talk to us about InfluxDB Clustered