Pushover event handler

This page documents an earlier version of Kapacitor. Kapacitor v1.6 is the latest stable version. View this page in the v1.6 documentation.

Pushover is a service that sends instant push notifications to phone and tablets. Kapacitor can be configured to send alert messages to Pushover.


Configuration as well as default option values for the Pushover event handler are set in your kapacitor.conf. Below is an example configuration:

  enabled = true
  token = "mysupersecrettoken"
  user-key = "myuserkey"
  url = ""


Set to true to enable the Pushover event handler.


Your Pushover API token.


Your Pushover USER_TOKEN.


The URL for the Pushover API. This should not need to be changed.


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

devicestringSpecific list of users’ devices rather than all of a users’ devices. Multiple device names may be separated by a comma.
titlestringThe message title. By default, the app’s name is used.
urlstringA supplementary URL to show with the message.
url-titlestringA title for a supplementary URL, otherwise just the URL is shown.
soundstringThe name of one of the sounds supported by the device clients to override the user’s default sound choice.

Example: handler file

id: handler-id
topic: topic-name
kind: pushover
  device: device1, device2, device3
  title: Alert from Kapacitor
  url-title: This is an example title
  sound: siren

Example: TICKscript

  // ...
    .device('device1, device2, device3')
    .title('Alert from Kapacitor')
    .URLTitle('This is an example title')

Pushover Priority Levels

Pushover expects priority levels with each alert. Kapacitor alert levels are mapped to the following priority levels:

Alert LevelPriority Level
OK-2 priority level.
Info-1 priority level.
Warning0 priority level.
Critical1 priority level.

Pushover Setup

Register your application with Pushover to get a Pushover token. Include the token in the [pushover] configuration section of your kapacitor.conf.

Using the Pushover event handler

With the Pushover event handler enabled and configured in your kapacitor.conf, use the .pushover() attribute in your TICKscripts to send alerts to Pushover or define a Pushover handler that subscribes to a topic and sends published alerts to Pushover.

Send alerts to Pushover from a TICKscript

The following TICKscript sends the message, “Hey, check your CPU”, to Pushover whenever idle CPU usage drops below 10% using the .pushover() event handler.


    .crit(lambda: "usage_idle" < 10)
    .message('Hey, check your CPU')
      .title('Alert from Kapacitor')

Send alerts to Pushover from a defined handler

The following setup sends an alert to the cpu topic with the message, “Hey, check your CPU”. A Pushover handler is added that subscribes to the cpu topic and publishes all alert messages to Pushover.

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%.


    .crit(lambda: "usage_idle" < 10)
    .message('Hey, check your 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 Pushover event handler to send alerts to Pushover.


id: pushover-cpu-alert
topic: cpu
kind: pushover
  title: Alert from Kapacitor
  sound: siren

Add the handler:

kapacitor define-topic-handler pushover_cpu_handler.yaml

Was this page helpful?

Thank you for your feedback!

Linux Package Signing Key Rotation

All signed InfluxData Linux packages have been resigned with an updated key. If using Linux, you may need to update your package configuration to continue to download and verify InfluxData software packages.

For more information, see the Linux Package Signing Key Rotation blog post.

State of the InfluxDB Cloud (IOx) documentation

The new documentation for InfluxDB Cloud backed by InfluxDB IOx 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.