kapacitord run

The kapacitord run starts and runs the Kapacitor server.


kapacitord run [flags]


-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


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:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.