Post (HTTP) event handler

The post event handler posts JSON encoded data to an HTTP endpoint.

Configuration

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

Post Settings in kapacitor.conf

[[httppost]]
  endpoint = "example"
  url = "http://example.com/path"
  headers = { Example = "your-key" }
  basic-auth = { username = "my-user", password = "my-pass" }
  alert-template = "{{.Message}}:{{range .Data.Series}}{{.Tags}},{{range .Values}}{{.}}{{end}}{{end}}"
  alert-template-file = "/path/to/template/file"
  row-template = "{{.Name}} host={{index .Tags \"host\"}}{{range .Values}} {{index . "time"}} {{index . "value"}}{{end}}"
  row-template-file = "/path/to/template/file"

  
   Copy
 Fill window

Name of a configured HTTP POST endpoint that acts as an identifier for [[httppost]] configurations when multiple are present. Endpoints are identifiers only. They are not appended to HTTP POST URLs.

`url`

The URL to which the alert data will be posted.

`headers`

Set of extra header values to set on the POST request.

`basic-auth`

Set of authentication credentials to set on the POST request.

`alert-template`

Alert template for constructing a custom HTTP body. Alert templates are only used with post alert handlers as they consume alert data. Skip to alert templating.

`alert-template-file`

Absolute path to an alert template file. Skip to alert templating.

`row-template`

Row template for constructing a custom HTTP body. Row templates are only used with the httpPost node pipeline nodes as they consume a row at a time. Skip to row templating.

`row-template-file`

Absolute path to a row template file. Skip to row templating.

Defining configuration options with environment variables

The endpoint, url, and headers configuration options can be defined with environment variables:

KAPACITOR_HTTPPOST_0_ENDPOINT = "example"
KAPACITOR_HTTPPOST_0_URL = "http://example.com/path"
KAPACITOR_HTTPPOST_0_HEADERS_Example1 = "header1"
KAPACITOR_HTTPPOST_0_HEADERS_Example2 = "header2"

  
   Copy
 Fill window

Configuring and using multiple HTTP POST endpoints

The kapacitor.conf supports multiple [[httppost]] sections. The endpoint configuration option of each acts as a unique identifier for that specific configuration. To use a specific [[httppost]] configuration with the Post alert handler, specify the endpoint in your post alert handler file, or your TICKscript.

kapacitor.conf

[[httppost]]
  endpoint = "endpoint1"
  url = "http://example-1.com/path"
  # ...

[[httppost]]
  endpoint = "endpoint2"
  url = "http://example-2.com/path"
  # ...

  
   Copy
 Fill window

Multiple HTTP POST endpoint configurations can also be added using environment variables. Variables values are grouped together using the number in each variable key.

KAPACITOR_HTTPPOST_0_ENDPOINT = "example0"
KAPACITOR_HTTPPOST_0_URL = "http://example-0.com/path"
KAPACITOR_HTTPPOST_0_HEADERS_Example1 = "header1"
KAPACITOR_HTTPPOST_0_HEADERS_Example2 = "header2"

KAPACITOR_HTTPPOST_1_ENDPOINT = "example1"
KAPACITOR_HTTPPOST_1_URL = "http://example-1.com/path"
KAPACITOR_HTTPPOST_1_HEADERS_Example1 = "header1"
KAPACITOR_HTTPPOST_1_HEADERS_Example2 = "header2"

  
   Copy
 Fill window

Options

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

Name	Type	Description
url	string	The URL to which the alert data will be posted.
endpoint	string	Name of a HTTP POST endpoint (configured in the `kapacitor.conf`) to use. Cannot be specified in place of the URL.
headers	map of string to string	Set of extra header values to set on the POST request.
capture‑response	bool	If the HTTP status code is not an `2xx` code, read and log the HTTP response.
timeout	duration	Timeout for the HTTP POST.
skipSSLVerification	bool	Disables SSL verification for the POST request.

Example: Handler file - Using a pre-configured endpoint

id: handler-id
topic: topic-name
kind: post
options:
  # Using the 'example' endpoint configured in the kapacitor.conf
  endpoint: example

  
   Copy
 Fill window

Example: Handler file - Defining post options “inline”

id: handler-id
topic: topic-name
kind: post
options:
  # Defining post options "inline"
  url: http://example.com/path
  headers:
    'Example1': 'example1'
    'Example2': 'example2'
  capture-response: true
  timeout: 10s
  skipSSLVerification: true

  
   Copy
 Fill window

Example: TICKscript - Using a pre-configured endpoint

|alert()
  // ...  
  // Using the 'example' endpoint configured in the kapacitor.conf
  .post()
    .endpoint('example')

  
   Copy
 Fill window

Example: TICKscript - Defining post options “inline”

|alert()
  // ...
  // Defining post options "inline"
  .post('https://example.com/path')
    .header('Example1', 'example1')
    .header('Example2', 'example2')
    .captureResponse()
    .timeout(10s)
    .skipSSLVerification()

  
   Copy
 Fill window

Using the Post event handler

The post event handler can be used in both TICKscripts and handler files to post alert and HTTP POST data to an HTTP endpoint. The examples below deal with alerts and use the same [[httppost]] configuration defined in the kapacitor.conf:

HTTP POST settings in kapacitor.conf

[[httppost]]
  endpoint = "api-alert"
  url = "http://mydomain.com/api/alerts"
  headers = { From = "alerts@mydomain.com" }
  alert-template = "{{.Message}}:{{range .Data.Series}}{{.Tags}},{{range .Values}}{{.}}{{end}}{{end}}"

  
   Copy
 Fill window

Post alerts from a TICKscript

The following TICKscripts use the .post() event handler to post the message, “Hey, check your CPU”, whenever idle CPU usage drops below 10%.

post-cpu-alert.tick

stream
  |from()
    .measurement('cpu')
  |alert()
    .crit(lambda: "usage_idle" < 10)
    .message('Hey, check your CPU')
    .post()
      .endpoint('api-alerts')

  
   Copy
 Fill window

If you don’t want to use the [[httppost]] settings defined in the kapacitor.conf, you can specify your post options inline.

post-cpu-alert.tick

stream
  |from()
    .measurement('cpu')
  |alert()
    .crit(lambda: "usage_idle" < 10)
    .message('Hey, check your CPU')
    .post('https://example.com/path')
      .header('Example1', 'example1')
      .header('Example2', 'example2')
      .captureResponse()
      .timeout(10s)
      .skipSSLVerification()

  
   Copy
 Fill window

Post alerts from a defined handler

The following setup sends an alert to the cpu topic with the message, “Hey, check your CPU”. A post handler is added that subscribes to the cpu topic and posts all alert messages to the url and endpoint defined in the kapacitor.conf.

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')

  
   Copy
 Fill window

Add and enable the TICKscript:

kapacitor define cpu_alert -tick cpu_alert.tick
kapacitor enable cpu_alert

  
   Copy
 Fill window

Create a handler file that subscribes to the cpu topic and uses the post event handler to post alerts to an HTTP endpoint.

post_cpu_handler.yaml

id: post-cpu-alert
topic: cpu
kind: post
options:
  url: 'http://example.com/path'
  headers:
    'From': 'alert@mydomain.com'

  
   Copy
 Fill window

Add the handler:

kapacitor define-topic-handler post_cpu_handler.yaml

  
   Copy
 Fill window

Post templating

The post event handler allows you to customize the content and structure of POSTs with alert and row templates.

Alert templates

Alert templates are used to construct a custom HTTP body. They are only used with post alert handlers as they consume alert data. Templates are defined either inline in the kapacitor.conf using the alert-template configuration or in a separate file and referenced using the alert-template-file config.

Alert templates use Golang Template and have access to the following fields:

Field	Description
.ID	The unique ID for the alert.
.Message	The message of the alert.
.Details	The details of the alert.
.Time	The time the alert event occurred.
.Duration	The duration of the alert event.
.Level	The level of the alert, i.e INFO, WARN, or CRITICAL.
.Data	The data that triggered the alert.
.PreviousLevel	The previous level of the alert, i.e INFO, WARN, or CRITICAL.
.Recoverable	Indicates whether or not the alert is auto-recoverable.

Inline alert template

kapacitor.conf

[[httppost]]
  endpoint = "host"
  url = "host={{index .ID \"host\"}}{{index . "time"}}{{end}}}"
  alert-template = "{{.Message}}:{{range .Data.Series}}{{.Tags}},{{range .Values}}{{.}}{{end}}{{end}}"

  
   Copy
 Fill window

Alert template file

kapacitor.conf

[[httppost]]
  endpoint = "host"
  url = "host={{index .ID \"host\"}}{{index . "time"}}{{end}}}"
  alert-template-file = "/etc/templates/alert.html"

  
   Copy
 Fill window

/etc/templates/alert.html

{{.Message}}:{{range .Data.Series}}{{.Tags}},{{range .Values}}{{.}}{{end}}{{end}}

  
   Copy
 Fill window

Row templates

Row templates are used to construct a custom HTTP body. They are only used with httpPost handlers as they consume a row at a time. Templates are defined either inline in the kapacitor.conf using the row-template configuration or in a separate file and referenced using the row-template-file config.

Row templates use Golang Template and have access to the following fields:

Field	Description
.Name	The measurement name of the data stream
.Tags	A map of tags on the data.
.Values	A list of values; each a map containing a “time” key for the time of the point and keys for all other fields on the point.

Inline row template

kapacitor.conf

[[httppost]]
  endpoint = "host"
  url = "host={{index .Tags \"host\"}}{{range .Values}} {{index . "time"}} {{index . "value"}}{{end}}"
  row-template = '{{.Name}} host={{index .Tags "host"}}{{range .Values}} {{index . "time"}} {{index . "value"}}{{end}}'

  
   Copy
 Fill window

Row template file

kapacitor.conf

[[httppost]]
  endpoint = "host"
  url = "host={{index .Tags \"host\"}}{{range .Values}} {{index . "time"}} {{index . "value"}}{{end}}"
  row-template-file = "/etc/templates/row.html"

  
   Copy
 Fill window

/etc/templates/row.html

{{.Name}} host={{index .Tags \"host\"}}{{range .Values}} {{index . "time"}} {{index . "value"}}{{end}}

  
   Copy
 Fill window

Was this page helpful?

Thank you for your feedback!

Support and feedback

Thank you for being part of our community! We welcome and encourage your feedback and bug reports for Kapacitor and this documentation. To find support, use the following resources:

Edit this page Submit docs issue Submit Kapacitor issue

Post (HTTP) event handler

Configuration

Post Settings in kapacitor.conf

`endpoint`

`url`

`headers`

`basic-auth`

`alert-template`

`alert-template-file`

`row-template`

`row-template-file`

Defining configuration options with environment variables

Configuring and using multiple HTTP POST endpoints

Options

Example: Handler file - Using a pre-configured endpoint

Example: Handler file - Defining post options “inline”

Example: TICKscript - Using a pre-configured endpoint

Example: TICKscript - Defining post options “inline”

Using the Post event handler

Post alerts from a TICKscript

Post alerts from a defined handler

Post templating

Alert templates

Inline alert template

Alert template file

Row templates

Inline row template

Row template file

Support and feedback

The future of Flux

InfluxDB 3 Core and Enterprise are now in Beta

Post (HTTP) event handler

Where are you running InfluxDB?

AWS

GCP

Azure

Default

Custom

Thank you for your feedback!

The future of Flux

InfluxDB 3 Core and Enterprise are now in Beta