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 → Configuration → Integrations → Private integration
2
Add Integration
Click Add an integration, select alert type
3
Configure Push URL
Copy the generated Push URL to your monitoring platform
Dedicated Integration Configuration
A dedicated integration belongs to the channel you created it in. To edit, enable or disable, or delete it, you need the “Channels Manage” or “Integrations Manage” permission. You must also be an account admin, the channel creator, or a member of the channel’s managing team.
Shared integration
Global integration created in the Integration Center, distributes alerts to different channels by 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 choose which channels receive the alerts
Shared Integration Configuration
Browsing and finding integrations
The Integration Center groups alert sources and change events by category. Narrow the list with a category chip, or search for the system you need. The add-integration panel has one set of chips per tab, and each tab opens on its own default category:- Integrations without a category appear under Uncategorized. Empty categories don’t appear.
- By default the panel keeps only All, Generic, the tab’s default category, and the currently selected category; the rest collapse into More N, which expands on click.
- Search matches integration names and types across all categories, ignoring the selected chip, and lists hits under Search results. Clear the search to return to your selected category.
All integrations catalog
Clicking the All chip opens a full-screen catalog:- The number next to the title is how many integrations the catalog covers, and the search box at the top searches all of them.
- The category rail on the left lists every category with its entry count; clicking one scrolls the right side to that category (and clears the search).
- The right side lists systems by category; click Add to open the new-integration page for that system.
Requesting an integration
If the system you need is not covered yet, click Submit a request in the fallback area to tell us what to support. This entry point is available on Flashduty SaaS only; private deployments do not show it.
After you submit, the dialog confirms receipt and says we’ll reply by email after review. Until then, connect the system with a generic integration.
Integration features
Optional configurations for both integration methods, configurable on the integration details page:Vendors that ride on another integration
Some vendors have no integration type of their own; they ingest through a compatible one. Their cards appear in the selection list next to the integration types. You can search for them by vendor name or by common aliases such asVSPC, PDU, WUG, UPS, OCP, Azure Sentinel, and Bro.
A vendor card opens the creation page of the borrowed integration type, and the doc panel on the right shows that vendor’s guide. Flashduty saves the borrowed integration type, not the vendor name. The 29 vendors below work this way.
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
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, and so on):- Dedicated Integration: No routing rules needed
- Shared Integration: Required; without it, Flashduty drops alerts
Rate limits
To ensure system stability, the gateway enforces the following rate limits on alert push APIs:Exceeding any of these limits returns a
429 status code — wait and retry. Contact technical support if you need higher limits.FAQ
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.
What happens to integrations after the subscription expires?
What happens to integrations after the subscription expires?
After the subscription expires, every integration (dedicated and shared) stops receiving alert events, and you can’t add new integrations. Flashduty keeps your configured integrations and resumes ingestion automatically after renewal, with no reconfiguration.
Related topics
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