Documentation

Exec event handler

The exec event handler executes an external program. Event data is passed over STDIN to the process.

Options

The following exec event handler options can be set in a handler file or when using .exec() in a TICKscript.

NameTypeDescription
progstringPath to program to execute.
argslist of stringList of arguments to the program.

Example: handler file

id: handler-id
topic: topic-name
kind: exec
options:
  prog: /path/to/executable
  args: 
    - 'executable arguments'

Example: TICKscript

|alert()
  // ...
  .exec('/path/to/executable', 'executable arguments')

Using the exec event handler

The exec event handler can be used in both TICKscripts and handler files to execute an external program based off of alert logic.

Note: Exec programs are run as the kapacitor user which typically only has access to the default system $PATH. If using an executable not in the $PATH, pass the executable’s absolute path.

Execute an external program from a TICKscript

The following TICKscript executes the sound-the-alarm.py Python script whenever idle CPU usage drops below 10% using the .exec() event handler.

exec-cpu-alert.tick

stream
  |from()
    .measurement('cpu')
  |alert()
    .crit(lambda: "usage_idle" < 10)
    .exec('/usr/bin/python', 'sound-the-alarm.py')

Execute an external program from a defined handler

The following setup sends an alert to the cpu topic with the message, “Hey, check your CPU”. An exec handler is added that subscribes to the cpu topic and executes the sound-the-alarm.py Python script whenever an alert message is published.

Create a TICKscript that publishes alert messages to a topic. The TICKscript below sends an alert message to the cpu topic any time idle CPU usage drops below 10%.

cpu_alert.tick

stream
  |from()
    .measurement('cpu')
  |alert()
    .crit(lambda: "usage_idle" < 10)
    .message('Hey, check your CPU')
    .topic('cpu')

Add and enable the TICKscript:

kapacitor define cpu_alert -tick cpu_alert.tick
kapacitor enable cpu_alert

Create a handler file that subscribes to the cpu topic and uses the exec event handler to execute the sound-the-alarm.py Python script.

exec_cpu_handler.yaml

id: exec-cpu-alert
topic: cpu
kind: exec
options:
  prog: '/usr/bin/python'
  args: 
    - 'sound-the-alarm.py'

Add the handler:

kapacitor define-topic-handler exec_cpu_handler.yaml

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

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