Planning channels
Proper planning can significantly improve operational efficiency.Creating a channel
Go to Channels → Create Channel. The wizard has four steps, and steps 2 and 3 are skippable — you can fill them in later from the channel details page. Step 4, Alert Grouping, cannot be skipped, but the wizard pre-selects a grouping method based on your subscription, which you can accept as is.Step 1: Channel information
1
Fill in Basic Information
Enter Channel Name, preferably named after business type or team
2
Select Owning Team
Select Owning Team, members of this team have full operational permissions for the channel
3
Set Managing Team (Optional)
If you need to delegate channel management permissions to other teams, set Managing Teams (up to 3). This feature is off by default; contact the Flashduty team to enable it. For the permission rules, see the FAQ on this page.
4
Set Access Level
- Public: Visible to all users in the account, can view and operate incidents but cannot modify channel configuration
- Private: Only visible to the owning team (or managing team), creator, and account administrators
Step 2: Configure an escalation rule (skippable)
Set up a default escalation rule for the new channel to decide who gets notified and how when an incident fires.- Notification recipients: choose from a schedule, a team, or an individual
- Notification template: required — select an enabled notification template
- Delay window: 0 – 3600 seconds, default 0; if the incident closes (automatically or manually) during the delay window, Flashduty sends no notification
- IM group chat channel (optional): simultaneously push to Feishu/Lark, Dingtalk, WeCom, Slack, Microsoft Teams, and similar group chats
Step 3: Ingest alert events (skippable)
Select one or more alert integrations (such as Zabbix, Prometheus, Alibaba Cloud Monitor) to attach to the current channel, and the system generates the corresponding Webhook addresses.- Selected integrations appear at the top of the step; before you pick any, the area reads “Selected integrations will appear here”
- Available integrations below can be filtered by name with the Search integrations box; a filter with no match shows “No matching integrations”, and an empty list shows “No integrations available”. Integrations whose visibility is private never appear in this list
Step 4: Alert grouping
Choose how the new channel merges alerts into incidents, and adjust the defaults. This step has no Skip button: saving the channel writes your choice into the new channel. The wizard pre-selects a grouping method for your subscription and marks that card with a Default badge. For which method each plan gets and which are available, see Configure noise reduction. You can keep the pre-selected defaults or adjust them here:
Click Save to create the channel.
If you skip steps 2 and 3, Flashduty creates only the channel. You can add or adjust escalation rules and integrations at any time from the channel details page. The alert grouping configuration from step 4 is saved with the channel.
Channel overview
On the channel details page, the Statistics module at the top shows 4 cards by default, based on the last 7 days with comparison to the previous period:
You can collapse the statistics cards. Open the Metric Analysis page for richer trends and dimension drill-downs.
Configuring core capabilities
After creating a channel, go to the Configuration tab on the details page. The tab uses a sidebar menu; see these pages for each capability:- Integrate alerts (Integrate Data → Dedicated Integrations): Integrate Data
- Escalation rules (Notification & Assignment → Escalation Rules): Configure Escalation Rules
- Noise reduction (Noise Reduction → Event Aggregation, Alert Grouping, Flapping Detection, Silence Rules, Inhibit Rules): Configure Noise Reduction
- Basic info and advanced settings (Settings): see Changing configuration below
Configure drop rules
Configure rules in Configuration → Integrate Data → Drop Rules to filter out events that have entered the channel but don’t need processing (such as test data or invalid alerts). Dropped events will not generate new alerts or merge into existing alerts.1
Create a Drop Rule
Click New rule in the upper-right corner of the page. The drop rule list is a table: click any row to expand it and view that rule’s drop conditions, and columns such as Last modified can be shown or hidden from the View menu. The Search name or description box above the list filters it by rule name and description, case-insensitively; it does not match the values inside conditions, and the list shows No matching results when nothing matches.
2
Fill in Rule Information
Enter a Rule Name (required) and Description (optional).
3
Set Filter Conditions
Configure filter conditions — supports matching by Integration Source and Severity.
4
Save the Rule
A saved rule is enabled by default. You can enable or disable any rule at any time from the drop rules list.
Flashduty runs drop rules in list order. If any rule matches, Flashduty drops the event.
Managing channels
Finding channels
- Click the Star on channel cards to bookmark frequently used channels
- Quickly locate target channels through Team Filter or My Favorites
-
Use the Sort by dropdown menu to order the list by the following fields:
- Select Sort in the upper-right corner, then drag channel cards to change the display order. The new order applies to all users
- The pager at the bottom right of the list switches the page size (12 / 24 / 48 / 96, default 24). You can also type a custom size, up to 100
Changing configuration
Go to Channel Details, then navigate to Configuration → Settings to modify configuration: Basic Info (Configuration → Settings → Basic Info):- Channel name, description
- Owning team
- Managing team (up to 3; contact the Flashduty team to enable it). Managing teams take over management permissions from the owning team
- Access level (public or private)
The free and standard plans hide the Outlier incident detection and External reporting toggles. The Close with alert recovery toggle is hidden by default; contact the Flashduty team to enable it.
Disabling and deleting
Handling incidents
Handle incidents in the Incident List tab:- Filter by Processing Status for triggered, acknowledged, closed, and so on.
- Select multiple incidents with the same status for Batch Close or Batch Acknowledge
- Use Merge to combine incidents pointing to the same root cause, supports cross-channel merging
FAQ
What's the difference between owning team, managing team, and access level?
What's the difference between owning team, managing team, and access level?
- Owning Team: The team that owns the channel and has full management permissions (edit, delete, and so on) by default
- Managing Team: Managing teams take over management permissions (edit, delete, and so on) from the owning team. Both teams keep read access. Contact the Flashduty team to enable this feature
- Access Level: Controls who can see the channel and its incidents. Public channels are visible to everyone but only the owning team (or managing team) can modify configuration; private channels are only visible to the owning team (or managing team)
Is incident data still available after deleting a channel?
Is incident data still available after deleting a channel?
No. Deleting a channel permanently deletes its configuration (integrations, escalation rules, and so on).
How many channels can I create on the free plan?
How many channels can I create on the free plan?
The free plan supports creating 1 channel only. Once a channel exists, Flashduty disables the Create Channel button and prompts you to upgrade. To create more channels, upgrade to the standard plan or above. Learn about subscription plans
Related topics
Integrate Data
Bring monitoring system alerts into the channel
Configure Escalation Rules
Define alert notification and escalation rules
Configure Noise Reduction
Reduce alert bombardment, improve processing efficiency