BigPanda event handler

BigPanda is an event correlation and automation platform that helps organizations prevent and resolve IT outages.


Configuration and default option values for the BigPanda event handler are set in your kapacitor.conf. The example below shows the default configuration:

  enabled = false
  # BigPanda integration App Key
  app-key = ""
  # Authorization Bearer token for BigPanda REST API.  
  token = ""
  # BigPanda Alert API url  
  url = ""  


Set to true to enable the BigPanda event handler.


Set your authorization Bearer token for BigPanda REST API.


Set your BigPanda integration App Key. To get your App Key, log in to your BigPanda account and select Integrations in the header toolbar, and then click the New Integration. Select Alerts REST API, click Integrate button, and then Create an App Key.


BigPanda Alert API URL.


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

appKeystringBigPanda appKey
primaryPropertystringBigPanda primary property
secondaryPropertystringBigPanda secondary property
hoststringHost alert payload parameter (object that caused the alert)
attributesmap of key value pairsOption to add additional attribute(s) to the alert payload

BigPanda uses the primary property to construct the title and the secondary property to construct the subtitle of an incident. See Alert Correlation Logic for more information.

By default, the handler maps the Kapacitor task and alert properties below to the BigPanda Alert or Event fields as follows:

ValueBigPanda Alert Field

All EventData tags and fields are appended to the BigPanda Alert as Additional attributes. For more information, see BigPanda Alert REST API.

TICKscript examples

    .crit(lambda: "usage_user" > 90)
    .message('Hey, check your CPU')
    .where(lambda: "cpu" == 'cpu-total')
  |eval(lambda: 100.0 - "usage_idle").as('total_used')
    .message('Hey {{ index .Tags "host"}} / {{ .ID }}: is high!')
    .details('{{ index .Tags "host"}}')
    .info(lambda: "total_used" > 70)
    .warn(lambda: "total_used" > 80)
    .crit(lambda: "total_used" > 90)
      .host('{{ }}')
      .attribute('monitor_link', '{{ }}')
      .attribute('x_total_used', '{{ .Fields.total_used }}')

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: