kapacitord run

The kapacitord run starts and runs the Kapacitor server.


kapacitord run [flags]


Flag Description Input
-blacklist-cidrs Blacklist CIDRs for most HTTP GET/POST operations Comma-separated list of CIDRs
-config Path to Kapacitor configuration file Configuration filepath
-disable-handlers Disable alert handlers Comma-separated list of alert-handlers
-hostname Override the hostname in the Kapacitor configuration file Hostname
-pidfile Write process ID to a file PID filepath
-log-file Write logs to a file Log filepath
-log-level Set the log level debug, info, or error


Run Kapacitor with default settings

kapacitord run

Run Kapacitor with custom configuration settings

kapacitord run -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 run -disable-handlers exec,mqtt

Change Kapacitor logging settings

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

Blacklist HTTP GET or POST operations from specific CIDRs

kapacitord run -blacklist-cidrs,

Was this page helpful?

Thank you for your feedback!

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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: