Integration Methods
Flashduty On-call offers two alert integration methods:| Comparison | Dedicated Integration | Shared Integration |
|---|---|---|
| Data Flow | Alerts go directly into the current channel | Distributed to one or more channels via routing rules |
| Configuration Difficulty | Out-of-the-box, no routing needed | Requires routing rule configuration |
| Typical Scenario | Single business team | Multiple businesses sharing monitoring platform |
| Recommended Choice | Just getting started, simple business | Alerts need to be distributed to different business channels based on conditions |
Dedicated Integration
Integration created within a channel, alerts automatically enter that channel.
Shared Integration
Global integration created in the Integration Center, distributes alerts to different channels via routing rules.
Integration Features
Optional configurations for both integration methods, configurable on the integration details page:| Feature | Description | Dedicated Integration | Shared Integration |
|---|---|---|---|
| Label Enhancement | Dynamically generate new labels through regex extraction, mapping tables, etc. | ✓ | ✓ |
| Alert Processing | Configure Pipeline to filter, modify, or drop alerts | ✓ | ✓ |
| Routing Rules | Distribute alerts to different channels based on conditions | ✗ | ✓ (Required) |
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
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
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
Rate Limits
To ensure system stability, each integration has the following request rate limits:| Limit Type | Limit Value |
|---|---|
| QPS | 100 requests/second |
| QPM | 1000 requests/minute |
Exceeding limits will return a
429 status code, please retry after waiting. Contact technical support if you need higher limits.FAQ
Not receiving alerts from shared integration?
Not receiving alerts from shared integration?
Is there a limit on the number of integrations?
Is there a limit on the number of integrations?
Currently no limit.
How are alert labels generated?
How are alert labels generated?
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.
How is the alert title determined? Can it be modified?
How is the alert title determined? Can it be modified?
Default is a combination of “Policy Name / Alert Resource”. For customization, refer to Reference Variables.
How to see which integration an alert came from?
How to see which integration an alert came from?
Go to Incident Details → Associated Alerts → Alert Source.