Documentation

TCP event handler

The TCP event handler sends JSON encoded alert data to a TCP endpoint.

Options

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

NameTypeDescription
addressstringAddress of TCP endpoint.

Example: handler file

id: handler-id
topic: topic-name
kind: tcp
options:
  address: 127.0.0.1:7777

Example: TICKscript

|alert()
  // ...
  .tcp('127.0.0.1:7777')

Using the TCP event handler

The TCP event handler can be used in both TICKscripts and handler files to send alert data to TCP endpoint.

Send alert data to a TCP endpoint from a TICKscript

The following TICKscript uses the .tcp() event handler to send alert data whenever idle CPU usage drops below 10%.

tcp-cpu-alert.tick

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

Send alert data to a TCP endpoint from a defined handler

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

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 TCP event handler to send alert data to a TCP endpoint.

tcp_cpu_handler.yaml

id: tcp-cpu-alert
topic: cpu
kind: tcp
options:
  address: 127.0.0.1:7777

Add the handler:

kapacitor define-topic-handler tcp_cpu_handler.yaml

Was this page helpful?

Thank you for your feedback!


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: