Planning Channels
Proper planning can significantly improve operational efficiency.| Scenario | Recommended Approach | Reason |
|---|---|---|
| Independent business teams | Create channels by team | Clean alert data, precise escalation rules |
| Multiple businesses sharing monitoring | Create channels by business module | Avoid configuration confusion, reduce misassignment |
Creating a Channel
Select Management Team
Select Management Team, members of this team have full operational permissions for the channel
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 management team, creator, and account administrators
Configure Auto-close Timeout (Optional)
- Auto-close after incident trigger: Timer starts from when the incident is first triggered, suitable for alerts without automatic recovery
- Auto-close after alerts stop merging: Timer starts from the last alert merge, suitable for scenarios with alert grouping enabled
Enable Outlier Incident Detection (Optional)
When enabled, incident lists and notification content will include an “Outlier Incident” indicator for quick identification. Learn more
You can skip escalation rules or integration configuration during creation and manage them later in the channel.
Configuring Core Capabilities
After creating a channel, complete the following configurations on the details page:Integrate Alerts
Create alert integrations in the Integrate Data tab to bring monitoring system alerts into this channel.- Each integration type generates an independent Webhook address
- Configure drop rules to filter test data or invalid alerts
Configure Escalation Rules
Define incident notification paths in the Escalation Rules tab: who to notify, how to notify, and how to escalate on timeout.- Multiple rules are matched from top to bottom by priority, matching stops on first match
- Drag to adjust rule order
Configure Noise Reduction
Converge massive alerts into fewer incidents in the Noise Reduction tab:| Capability | Description |
|---|---|
| Alert Grouping | Merge similar alerts from the same host or service into one incident |
| Flapping Detection | Automatically identify and suppress alerts that oscillate repeatedly in a short time |
| Silence Rules | Temporarily suppress alert notifications under specific conditions during scheduled maintenance windows or specific time periods |
| Inhibit Rules | Reduce redundant notifications using dependencies between alerts |
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 function in the upper right corner to adjust channel order, only affects current user
Changing Configuration
Go to Channel Details → Basic Settings to modify:- Channel name, description
- Management team
- Auto-close timeout policy
Disabling and Deleting
| Action | Description |
|---|---|
| Disable | Stop receiving new alerts, preserve historical data and configuration |
| Delete | Permanently destroy channel and all configuration, including incident data, irreversible |
Handling Incidents
Handle incidents in the Incident List tab:- Filter by Processing Status for triggered, acknowledged, closed, etc.
- 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 management team and access level?
What's the difference between management team and access level?
- Management Team: Controls who can modify channel configuration (integrations, escalation rules, noise reduction rules, etc.)
- Access Level: Controls who can see the channel and its incidents. Public channels are visible to everyone but only the management team can modify configuration; private channels are only visible to the management team
How to choose between the two auto-close timeout policies?
How to choose between the two auto-close timeout policies?
- If the alert source doesn’t have automatic recovery events and alert grouping is not enabled, choose Auto-close after incident trigger
- If alert grouping is enabled, choose Auto-close after alerts stop merging to ensure all alerts within the grouping window are processed
Is incident data still available after deleting a channel?
Is incident data still available after deleting a channel?
No, channel configuration (integrations, escalation rules, etc.) will be permanently deleted and cannot be recovered.