Documentation

Publish event handler

The publish event handler publishes events to another topic.

Options

The following publish event handler options can be set in a handler file.

NameTypeDescription
topicslist of stringList of topic names to publish events.

Example: handler file

id: handler-id
topic: topic-name
kind: publish
options:
  topics:
    - system
    - ops_team

Using the publish event handler

The following setup sends an alert to the cpu topic with the message, “Hey, check your CPU”. A publish handler is added that subscribes to the cpu topic and publishes new alerts to other topics.

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 publish event handler to publish alerts to other topics.

publish_cpu_alerts_handler.yaml

id: publish-cpu-alert
topic: cpu
kind: publish
options:
  topics:
    - system
    - ops_team

Add the handler:

kapacitor define-topic-handler publish_cpu_alerts_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 November 3, 2025, 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