Documentation

kapacitord

The kapacitord daemon starts and runs the Kapacitor server.

Usage

kapacitord [[command] [flags]]

Commands

CommandDescription
configDisplay the default Kapacitor configuration
downgradeReverts a topic store format upgrade
helpOutput help for a command
runRun the Kapacitor server
versionDisplay the Kapacitor version

run is the default command.

Flags

FlagDescriptionInput
-blacklist-cidrsBlacklist CIDRs for most HTTP GET/POST operationsComma-separated list of CIDRs
-configPath to Kapacitor configuration fileConfiguration filepath
-disable-handlersDisable alert handlersComma-separated list of alert-handlers
-hostnameOverride the hostname in the Kapacitor configuration fileHostname
-pidfileWrite process ID to a filePID filepath
-log-fileWrite logs to a fileLog filepath
-log-levelSet the log leveldebug, info, or error

Examples

Run Kapacitor with default settings

kapacitord

Run Kapacitor with custom configuration settings

kapacitord -config /path/to/kapacitor.conf

Disable alert handlers

Disabling alert handlers can be useful for security reasons–for example, disabling the exec handler on a shared system.

kapacitord -disable-handlers exec,mqtt

Change Kapacitor logging settings

kapacitord \
  -log-file /path/to/kapacitor.log \
  -log-level debug

Blacklist HTTP GET or POST operations from specific CIDRs

kapacitord -blacklist-cidrs 10.10.0.0/16,192.168.200.5/30

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