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!


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.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: