Skip to main content
Filter conditions select alerts or incidents by field value; only those that match are handled by the rule they belong to. For how to write one, see How to configure filter conditions?.

Where are filter conditions used?

Filter conditions apply to the following scenarios:

How to configure filter conditions?

Rule design

A filter consists of one or more condition groups:
  • Conditions within a group: AND relationship—each condition must match for the group to match
  • Between groups: OR relationship—any group matching means overall match
Each condition has a field, an operator, and target values. There are two operators:
  • Match: Target can have multiple values; if any value satisfies the condition, that condition matches
  • Not Match: Target can have multiple values; if all values don’t satisfy the condition, that condition matches
The specific matching method is decided by the target-value format. See Matching methods.

Available fields

Filter condition keys fall into two categories: Filter Condition Example As shown above, there are two condition groups, each with two conditions, and the conditions have multiple match values:
  • Group 1: severity matches Critical or Warning, and labels.check matches Binlog Sync Delay
  • Group 2: labels.check matches any of /cpu/, /io/, or /disk/, and labels.value matches num:gt:90
The filter matches when either group matches.

Matching methods

Target values are always strings; the format decides the matching method: regex, wildcard, CIDR (IP range), or numeric comparison, and anything else is an exact match. The condition editor lists the available methods directly under the input; the fourth one is labelled CIDR Matching in the UI.
When a value string has / as prefix and suffix, Flashduty treats the entire value as regex.Example:
  • labels.check: /outage/ — matches when check label contains “outage”
Flashduty uses RE2 regex specification platform-wide. Some Perl syntax may not match. You can use AI Chatbot to generate expressions and verify at RE2 Playground.
CIDR and numeric matching don’t apply in: incident list filtering by labels, alert list filtering by labels, and alert inhibit rule filtering for active alerts.

FAQ

Flashduty On-call receives large volumes of data. To ensure system stability, the system only searches the most recent 500 alert events from the past 24 hours for label deduplication. Therefore, extracted labels may change dynamically, or no labels may be extracted if there’s no new data in the past 24 hours.In this case, you can manually enter labels.