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 → 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

Dedicated Integration Configuration

A dedicated integration belongs to the channel it was created in: editing, enabling/disabling, and deleting it requires the “Channels Manage” or “Integrations Manage” functional permission together with the data permission for that channel — only account admins, the channel creator, or the channel’s managing team can operate. Other members see these buttons disabled, with the reason on hover.

​
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

​
Browsing and Finding Integrations

The Integration Center groups the alert sources and change events it covers by category, so you can 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 with no registered category are collected under Uncategorized; a category with no entries is not shown.
  • 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.
  • The search box matches across all categories (ignoring the selected chip) by integration name or type, and shows the hits as Search results; clearing the search returns you to the category you had selected.

​
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 lays out cards by category (logo, name, and a two-line blurb); hovering a card reveals Add, which opens the new-integration page for that system.
At the bottom the catalog keeps a “Can’t find your system?” fallback area with two ways out: connect it with a generic integration, or request an integration.

​
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 that the request was received and explains that we will reply by email after review; until the request is supported, you can 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 above alongside the integration types, and they are searchable too — by vendor name and by common aliases such as VSPC, PDU, WUG, UPS, OCP, Azure Sentinel, and Bro. Opening a vendor card still lands on the creation page of the borrowed integration type, with the right-hand doc panel showing that vendor’s own guide; what gets saved is 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
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, the gateway enforces the following rate limits on alert push APIs:
Exceeding any of these limits returns a 429 status code — please wait and retry. 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.
After the subscription expires, every integration (dedicated and shared) stops receiving alert events, a persistent subscription-expired banner appears at the top of the Integration Center, and the cards for adding a new integration are disabled (hover for the reason). Configured integrations are not deleted, and ingestion resumes automatically after renewal — no reconfiguration needed.

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