Alert Pipeline

Alert Processing Pipeline allows you to cleanse, transform, and filter alert data at the moment it enters Flashduty On-call (integration layer). It acts like a data processing factory, ensuring alerts flowing into channels are standardized, clear, and valuable.

​

Processing Order

After an alert event enters Flashduty, it passes through three stages in sequence: Since label enhancement runs before Pipeline, Pipeline match conditions can reference labels added or modified during the enrichment stage.

​

How It Works

Pipeline sits between Label Enhancement and Route Distribution. Its execution logic is as follows:

1. Chain Processing: You can configure multiple processing rules that execute sequentially from top to bottom
2. Input/Output: The result of a previous rule (e.g., modified title) can serve as input for the next rule
3. Layer Positioning: Pipeline operates at the integration layer. This means once rules take effect, all alerts ingested through this integration will be affected, regardless of which channel they’re ultimately routed to

​

Configuration Entry

Go to Integration Center => Select created integration => Alert Processing tab.

​

Core Features and Scenarios

​

Custom Severity

Flashduty On-call has built-in severity mapping for standard integrations (e.g., mapping Zabbix High to Critical). But if default rules don’t meet your needs, you can override them via Pipeline. Scenario: Warning level alerts in the monitoring system are actually critical for core payment business and need to be upgraded to Critical to trigger phone notifications.

​

Information Rewrite

Convert cryptic machine language to human-readable business language using template syntax.

​

Alert Discard

Discard directly before data storage, leaving no records. This is similar to “Exclusion Rules” in channels but takes effect earlier.

​

Alert Inhibition

Pipeline’s inhibition feature is similar to channel inhibit rules, both supporting dependency-based inhibition based on source alert, target alert, and correlation conditions. Note that Pipeline inhibition only matches source alerts within the same integration, while channel inhibition matches across all alerts in the channel.

​

Reference Historical Data

When editing alert processing rules, the right side of the page provides a Related Alerts panel showing historical alert data ingested through the current integration. You can write processing rules while referencing actual alert content, ensuring that condition expressions and action configurations meet expectations. Click the Reference Historical Data button in the upper right of the editing page to open or close the related alerts panel. The panel supports drag-to-resize, allowing you to flexibly switch between the editing area and data preview.

​

Reference Syntax

When rewriting titles or descriptions, you can use Go Template syntax to reference internal alert variables. Proper use of variable references makes your alert notifications more dynamic and informative.

​

Further Reading