Suppress Kapacitor alerts based on hierarchy

Kapacitor allows you to build out a robust monitoring and alerting solution with multiple “levels” or “tiers” of alerts. However, an issue arises when an event triggers both high-level and low-level alerts and you end up getting multiple alerts from different contexts. The AlertNode’s .inhibit() method allows you to suppress other alerts when an alert is triggered.

For example, let’s say you are monitoring a cluster of servers. As part of your alerting architecture, you have host-level alerts such as CPU usage alerts, RAM usage alerts, disk I/O, etc. You also have cluster-level alerts that monitor network health, host uptime, etc.

If a CPU spike on a host in your cluster takes the machine offline, rather than getting a host-level alert for the CPU spike and a cluster-level alert for the offline node, you’d get a single alert – the alert that the node is offline. The cluster-level alert would suppress the host-level alert.

Using the .inhibit() method to suppress alerts

The .inhibit() method uses alert categories and tags to inhibit or suppress other alerts.

// ...
    .inhibit('<category>', '<tags>')

The category for which this alert inhibits or suppresses alerts.

A comma-delimited list of tags that must be matched in order for alerts to be inhibited or suppressed.

Example hierarchical alert suppression

The following TICKscripts represent two alerts in a layered alert architecture. The first is a host specific CPU alert that triggers an alert to the system_alerts category whenever idle CPU usage is less than 10%. Streamed data points are grouped by the host tag, which identifies the host the data point is coming from.


    .crit(lambda: "usage_idle" < 10.0)

The following TICKscript is a cluster-level alert that monitors the uptime of hosts in the cluster. It uses the deadman() function to create an alert when a host is unresponsive or offline. The .inhibit() method in the deadman alert suppresses all alerts to the system_alerts category that include a matching host tag, meaning they are from the same host.


  |deadman(0.0, 1m)
    .inhibit('system_alerts', 'host')

With this alert architecture, a host may be unresponsive due to a CPU bottleneck, but because the deadman alert inhibits system alerts from the same host, you won’t get alert notifications for both the deadman and the high CPU usage; just the deadman alert for that specific host.

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: