Documentation

kapacitor replay

The kapacitor replay command replays a task or query recording.

The times of the data points will either be relative to now or, if the -rec-time flag is included, the exact times in the recording. In either case, relative times between data points remain the same.

Usage

kapacitor replay [flags]

Flags

FlagDescription
-no-waitRun replay in the background
-real-clockReplay data in real time, otherwise replay data as fast as possible
-rec-timeUse times saved in the recording instead of present times
-recordingRequired: Recording ID to replay
-replay-idID to assign to the replay (default is a random ID)
-taskTask ID

Examples

Replay a recording
kapacitor replay \
  -recording 4e0f09c5-1426-4778-8f9b-c4a88f5c2b66 \
  -task cpu_alert

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.8

Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

See the Blog Post

InfluxDB 3.8 is now available for both Core and Enterprise, alongside the 1.6 release of the InfluxDB 3 Explorer UI. This release is focused on operational maturity and making InfluxDB easier to deploy, manage, and run reliably in production.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On April 7, 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