Skip to main content
Flashduty On-call doesn’t generate alerts itself but serves as a unified alert center, receiving alert events from monitoring systems like Zabbix, Prometheus, Nightingale, and major cloud providers. Once integrated, you can use noise reduction, assignment, notification, analysis, and automation capabilities.

​
Integration Methods

Flashduty On-call offers two alert integration methods:

​
Dedicated Integration

Integration created within a channel, alerts automatically enter that channel.
1

Enter Integration Page

Go to Channel Details → Integrate Data → Dedicated Integration
2

Add Integration

Click Add Integration, select alert type
3

Configure Push URL

Copy the generated Push URL to your monitoring platform
Dedicated Integration

Dedicated Integration Configuration

​
Shared Integration

Global integration created in the Integration Center, distributes alerts to different channels via routing rules.
1

Enter Integration Center

Go to Integration Center → Alert Events → Add Integration
2

Create Integration

Select alert type, set Management Team (optional)
3

Configure Push URL

Copy the generated Push URL to your monitoring platform
4

Configure Routing Rules

Configure Routing Rules to specify which channel alerts should be distributed to
Shared integrations must have at least one routing rule configured, otherwise alerts will be dropped. We recommend setting up a rule without filter conditions as a fallback to prevent alert loss.
Shared Integration

Shared Integration Configuration

​
Integration Features

Optional configurations for both integration methods, configurable on the integration details page:

​
Label Enhancement

After alerts enter the system, automatically add or modify labels for subsequent routing, searching, and analysis. Multiple enhancement methods supported:
  • Regex Extraction: Extract key information from existing fields to generate new labels
  • Mapping Table: Generate labels through predefined key-value mappings
  • Combination: Add fixed label values to alerts
See Label Enhancement for details.

​
Alert Processing

Pre-process alerts through Pipeline, executing custom logic before alerts generate incidents:
  • Modify: Adjust alert title, severity, description, and other attributes
  • Filter: Drop unwanted alerts based on conditions
See Alert Processing for details.

​
Routing Rules

Distribute alerts to different channels based on alert attributes (such as labels, severity, etc.):
  • Dedicated Integration: No routing rules needed
  • Shared Integration: Required, otherwise alerts will be dropped
See Routing Rules for details.

​
Rate Limits

To ensure system stability, each integration has the following request rate limits:
Exceeding limits will return a 429 status code, please retry after waiting. Contact technical support if you need higher limits.

​
FAQ

  1. Check if routing rules are configured
  2. Confirm the source platform is triggering alert events normally
Currently no limit.
Flashduty On-call follows the “capture everything relevant” principle, putting key information into labels, description, or title. For dynamically generating other labels, configure Label Enhancement.
Default is a combination of “Policy Name / Alert Resource”. For customization, refer to Reference Variables.
Go to Incident Details → Associated Alerts → Alert Source.

Configure Escalation Rules

Define alert notification and escalation rules

Configure Noise Reduction

Reduce alert bombardment, improve processing efficiency

Alert Integration Guide

Learn specific integration methods for various monitoring platforms