Documentation

kapacitor CLI

The kapacitor CLI interacts with and manages the Kapacitor server.

Usage

kapacitor [command] [flags] [args]

Commands

CommandDescription
backupBackup the Kapacitor database
defineCreate or update a task
define-templateCreate or update a template
define-topic-handlerCreate or update an alert handler for a topic
deleteDelete Kapacitor resources
disableDisable a task
enableEnable a task
fluxManage Kapacitor Flux tasks
helpPrint help for a command
levelSet the logging level on the kapacitord server
listList information about Kapacitor resources
logsOutput Kapacitor logs
recordRecord the results of a task or query
reloadReload a task with an updated task definition
replayReplay a recording to a task
replay-liveReplay data to a task without recording it
service-testsRun service tests
showDisplay information about a task
show-templateDisplay information about a template
show-topicDisplay information about an alert topic
show-topic-handlerDisplay information about an alert handler for a topic
statsDisplay Kapacitor server statistics
varsPrint Kapacitor debug vars in JSON format
versionDisplay the Kapacitor version
watchWatch logs for a task

Flags

FlagDescriptionEnvironment variable
-skipVerifyDisable SSL or TLS verificationKAPACITOR_UNSAFE_SSL
-urlURL of the kapacitord server (default is http://localhost:9092)KAPACITOR_URL

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

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