Documentation

Talk event handler

This page documents an earlier version of Kapacitor. Kapacitor v1.6 is the latest stable version.

Deprecated

The Talk event handler is deprecated in Kapacitor 1.5.

Talk is a service that aggregates information into a centralized hub. Kapacitor can be configured to send alert messages to Talk.

Configuration

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

[talk]
  enabled = true
  url = "https://jianliao.com/v2/services/webhook/uuid"
  author_name = "Kapacitor"

enabled

Set to true to enable the Talk event handler.

url

The Talk webhook URL.

author_name

The default authorName.

Options

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

NameTypeDescription
TitlestringMessage title.
TextstringMessage text.

Example: handler file

id: handler-id
topic: topic-name
kind: talk
options:
  title: 'Message Title'
  text: 'This is the text included in the message.'

Example: TICKscript

|alert()
  // ...
  .talk()
    .title('Message Title')
    .text('This is the text included in the message.')

Talk Setup

Create a new incoming webhook to allow Kapacitor to send alerts to Talk.

  1. Sign into your Talk account.
  2. Under the “Team” tab, click “Integrations”.
  3. Select “Customize service” and click the Incoming Webhook “Add” button.
  4. Choose the topic to connect with and click “Confirm Add” button.
  5. Once the service is created, you’ll see the “Generate Webhook url”.
  6. Place the generated Webhook URL as the url in the [talk] section of your kapacitor.conf.

Using the Talk event handler

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

Send alerts to Talk from a TICKscript

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

talk-cpu-alert.tick

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

Send alerts to Talk from a defined handler

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

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 Talk event handler to send alerts to Talk.

talk_cpu_handler.yaml

id: talk-cpu-alert
topic: cpu
kind: talk
options:
  title: Alert from Kapacitor

Add the handler:

kapacitor define-topic-handler talk_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.

InfluxDB Cloud backed by InfluxDB IOx

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by IOx, this is the correct documentation.

If powered by TSM, see the TSM-based InfluxDB Cloud documentation.

InfluxDB Cloud backed by InfluxDB TSM

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine which enables nearly unlimited series cardinality and SQL query support. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by TSM, this is the correct documentation.

If powered by IOx, see the IOx-based InfluxDB Cloud documentation.

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.