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 integration, select alert type
3

Configure Push URL

Copy the generated Push URL to your monitoring platform
Dedicated Integration

Dedicated Integration Configuration

The list shows one row per integration in the channel; click an integration name to open its details. What each column means: The Search integration name box above the list filters the current list by integration name; the row order does not change while searching.
A dedicated integration belongs to the channel you created it in. To create, edit, enable or disable, delete, or rotate the key of a dedicated integration, you need the “Channels Manage” permission. You must also be an account admin, the channel creator, or a member of the channel’s managing team. “Integrations Manage” covers shared integrations in the Integration Center only; it does not apply to a dedicated integration.
You can manage dedicated integrations from the command line too: flashduty channel integration-list <channel-id> lists them, integration-create adds one, and integration-key-rotate rotates its key. See CLI for all 8 subcommands and their field limits.

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
A shared integration needs at least one routing rule, or Flashduty drops its alerts. Add a rule without filter conditions as a fallback so no alert is lost.
Shared Integration

Shared Integration Configuration

Browsing and finding integrations

The Integration Center groups alert sources and change events by category. Browse the categories, or search for the system you need.
  • The add-integration panel renders one collapsible section per category. Only the tab’s default category starts expanded (Popular on Alert Events, CI/CD & deploy on Change Events); click a title to expand the others.
  • Search matches integration names and types across every category: each category with hits stays on screen with its matching entries, the section header shows hits out of that category’s total (for example, 3 / 12), and the matching part of a name is highlighted. Search skips Popular, whose entries already live in their real categories.
  • When nothing matches, the panel shows No results for ”…”. The Alert Events tab also offers Standard alert event (connects any system through a Webhook), and every tab can use Request an integration (SaaS only). The search term is carried into the form as the system name.
  • View all, next to the search box, opens the full catalog: category navigation on the left, systems grouped by category on the right with each header showing the entry count. Hovering a card reveals a + in its top-right corner; clicking the card opens that integration’s new-integration page. Searching inside the catalog also groups hits by category with hits out of total; with no match it shows only the empty state, since the fallback area at the bottom already offers the buttons.
If the system you need is not listed, connect it with a generic integration, or click Submit a request at the bottom of the catalog. Submit a request is available on Flashduty SaaS only; private deployments do not show it. Field limits: system name 100, website or docs link 500 (must start with http:// or https://), notes 2000, work email 200 characters; the work email is not needed when your account already has an email.

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 as VSPC, 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
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, and so on):
  • Dedicated Integration: No routing rules needed
  • Shared Integration: Required; without it, Flashduty drops alerts
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 — 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 puts the key information pushed by the alert source 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, and you can’t add new integrations. Flashduty keeps your configured integrations and resumes ingestion automatically after renewal, with no reconfiguration.

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