Documentation

Log event handler

The log event handler writes to a specified log file with one alert event per line. If the specified log file does not exist, it will be created.

Options

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

Name Type Description
path string Absolute path to the log file.
mode int File mode and permissions to use when creating the file. Default is 0600. The leading 0 is required to interpret the value as an octal integer.

Example: handler file

id: handler-id
topic: topic-name
kind: log
options:
  path: '/tmp/alerts.log'
  mode: 0644

Example: TICKscript

|alert()
  // ...
  .log('/tmp/alerts.log')
    .mode(0644)

Using the log event handler

The log event handler can be used in both TICKscripts and handler files to log messages to a log file.

Log messages from a TICKscript

The following TICKscript uses the .log() event handler to log a message to the /tmp/alerts.log log file whenever idle CPU usage drops below 10%.

log-cpu-alert.tick

stream
  |from()
    .measurement('cpu')
  |alert()
    .crit(lambda: "usage_idle" < 10)
    .message('{{ .Time }}: CPU usage over 90%')
    .log('/tmp/alerts.log')

Log messages from a defined handler

The following setup sends an alert to the cpu topic with the message, “’{{ .Time }}: CPU usage over 90%’”. A log handler is added that subscribes to the cpu topic and logs messages to /tmp/alerts.log whenever a new 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('{{ .Time }}: CPU usage over 90%')
    .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 log event handler to log messages to the /tmp/alerts.log log file.

log_cpu_handler.yaml

id: log-cpu-alert
topic: cpu
kind: log
options:
  path: '/tmp/alerts.log'

Add the handler:

kapacitor define-topic-handler log_cpu_handler.yaml

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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: