Documentation

BigPanda event handler

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

Configuration

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

[bigpanda]
  enabled = false
  # BigPanda integration App Key
  app-key = ""
  # Authorization Bearer token for BigPanda REST API.  
  token = ""
  # BigPanda Alert API url  
  url = "https://api.bigpanda.io/data/v2/alerts"  

enabled

Set to true to enable the BigPanda event handler.

token

Set your authorization Bearer token for BigPanda REST API.

app-key

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.

url

BigPanda Alert API URL.

Options

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

NameTypeDescription
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
idcheck
messagedescription
detailsdetails
TaskNametask

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

TICKscript examples

stream
  |from()
    .measurement('cpu')
  |alert()
    .id('cpu_usage')
    .crit(lambda: "usage_user" > 90)
    .stateChangesOnly()
    .message('Hey, check your CPU')
    .bigPanda()
stream
  |from()
    .database('telegraf')
    .retentionPolicy('autogen')
    .measurement('cpu')
    .groupBy('host')
    .where(lambda: "cpu" == 'cpu-total')
  |eval(lambda: 100.0 - "usage_idle").as('total_used')
  |window().period(10s).every(10s)
  |mean('total_used').as('total_used')
  |alert()
    .id('cpu_usage_check')
    .message('Hey {{ index .Tags "host"}} / {{ .ID }}: is high!')
    .details('https://example.com/dashboard/{{ index .Tags "host"}}')
    .info(lambda: "total_used" > 70)
    .warn(lambda: "total_used" > 80)
    .crit(lambda: "total_used" > 90)
    .stateChangesOnly()
    .appKey('...')
    bigPanda()
      .host('{{ .Tags.host }}')
      .attribute('monitor_link', 'http://example.com/monitor?node={{ .Tags.host }}')
      .attribute('x_total_used', '{{ .Fields.total_used }}')

Was this page helpful?

Thank you for your feedback!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

View the release notes
Download Telegraf Controller v0.0.6-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2