Alert Channels
Receive alerts where your team works.
Overview
Alert notifications are delivered through named destinations and personal email subscriptions. Each destination is a named integration (e.g. "Ops Slack", "PagerDuty Critical") configured at the organization or project level.
Supported Channels
- Slack - Post to channels via incoming webhook
- Discord - Webhook-based notifications
- Microsoft Teams - Incoming webhook integration
- Mattermost - Self-hosted chat notifications
- Webhooks - Custom integrations
- Email - Personal per-member subscription
Destination Groups
Each destination belongs to a delivery group:
| Group | Description |
|---|---|
| Primary | Receives notifications immediately when an incident is created or updated |
| Backup | Receives critical escalation after 30 minutes without acknowledgment |
Backup destinations require Critical severity. They do not imply provider-failure failover.
Managing Destinations
View Destinations
- Go to Monitoring > Alerts > Notifications
- View all destinations configured in the current scope (organization or project)
Team channel destinations and your personal email subscription are shown in separate sections.
Create a Destination
- Go to Monitoring > Alerts > Notifications
- Click Add destination
- Enter a name, select the channel type and delivery group
- Choose which severities trigger this destination (at least one required)
- Paste the webhook URL (HTTPS required)
- Save the destination
The webhook URL is write-only — it is never returned by the API after creation.
Edit a Destination
- Click a destination to open its settings drawer
- Update name, enabled state, delivery group or severities
- Optionally replace the webhook URL (omit to keep the existing URL)
- Save changes
Changing the channel type requires creating a new destination.
Delete a Destination
- Open the destination settings
- Click Delete
- Confirm the deletion
Test a Destination
- Open the destination settings
- Click Test
- Review the result: Accepted, Failed or Uncertain
An accepted result means the provider accepted the request, not that a person received it. Uncertain means delivery could not be confirmed.
Enable / Disable
Toggle the enabled state on a destination to pause or resume notifications without deleting the configuration.
Slack Integration
Setup Steps
- Go to your Slack workspace
- Create an incoming webhook:
- Go to Apps > Incoming Webhooks
- Or visit
https://your-workspace.slack.com/apps/A0F7XDUAZ
- Click Add to Slack
- Choose a channel
- Copy the webhook URL
Configure in SailOps
- Go to Monitoring > Alerts > Notifications
- Click Add destination
- Select Slack as the channel
- Paste the webhook URL
- Choose severities and delivery group
- Test and save
Discord Integration
Setup Steps
- Open Discord
- Go to channel settings
- Select Integrations > Webhooks
- Click New Webhook
- Copy the webhook URL
Configure in SailOps
- Go to Monitoring > Alerts > Notifications
- Click Add destination
- Select Discord as the channel
- Paste the webhook URL
- Choose severities and delivery group
- Test and save
Microsoft Teams Integration
Setup Steps
- Open Microsoft Teams
- Go to the channel for alerts
- Click ... > Connectors
- Find Incoming Webhook
- Click Configure
- Name the connector and copy URL
Configure in SailOps
- Go to Monitoring > Alerts > Notifications
- Click Add destination
- Select Microsoft Teams as the channel
- Paste the webhook URL
- Choose severities and delivery group
- Test and save
Mattermost Integration
Setup Steps
- Go to Mattermost Integrations
- Click Incoming Webhooks
- Create new webhook
- Select channel
- Copy the webhook URL
Configure in SailOps
- Go to Monitoring > Alerts > Notifications
- Click Add destination
- Select Mattermost as the channel
- Paste the webhook URL
- Choose severities and delivery group
- Test and save
Email Subscriptions
Each member can subscribe to email notifications independently:
- Go to Monitoring > Alerts > Notifications
- In the email subscription section, toggle your subscription on or off
- Enabling requires a verified email address on your identity
Email subscriptions are personal — you can only manage your own, and your subscription state is never visible to other members. Disabling records an explicit opt-out for the current scope. Organization and project subscriptions are independent; an opt-out at the project level does not affect the organization subscription.
Webhooks (Custom Integration)
Use Cases
- Custom alerting systems
- SIEM integration
- PagerDuty, Opsgenie
- Internal tools
- Automation triggers
Configure Webhook
- Go to Monitoring > Alerts > Notifications
- Click Add destination
- Select Webhook as the channel
- Enter your webhook endpoint URL (HTTPS required)
- Choose severities and delivery group
- Test and save
Alerts are sent as HTTP POST requests to your endpoint.
Delivery Behavior
Parallel Delivery
All enabled destinations receive notifications in parallel. A failure in one destination does not block others.
Delivery Statuses
| Status | Description |
|---|---|
| Pending | Notification queued for delivery |
| Accepted | Provider accepted the request |
| Failed | Delivery failed after retries |
| Uncertain | Delivery could not be confirmed |
| Cancelled | Delivery was cancelled (e.g. maintenance window) |
| Suppressed | Delivery was suppressed (e.g. duplicate) |
Scope and Inheritance
Destinations are configured at the organization or project level. The Notifications page in the Alert Center shows destinations in the selected scope. When viewing a resource's alerts, the page explains that organization or project configuration may also apply.
Maintenance Windows
Maintenance windows pause notification delivery while observation continues. See Alerts Overview for details on creating and managing maintenance windows.
Best Practices
1. Use Primary and Backup Groups
Primary: Slack #ops-alerts → All severities
Backup: PagerDuty → Critical only (escalates after 30 min)
2. Test Before Relying on Destinations
Always test after creating or updating a destination.
3. Separate Critical from Noise
Create separate destinations for different severity levels:
- A Slack channel for all alerts
- A PagerDuty integration for critical only
4. Review Delivery Outcomes
Check the delivery section in the incident inspector to confirm notifications reached your team.
5. Review Periodically
- Remove unused destinations
- Update webhook URLs if changed
- Verify email subscriptions after team changes
Troubleshooting
Not Receiving Notifications
- Check that the destination is enabled
- Verify notifications are activated on the relevant rules (seven-day observation required for metric rules)
- Test the destination
- Check that no maintenance window is suppressing delivery
Delivery Shows "Uncertain"
The provider accepted the request but SailOps could not confirm final delivery. This does not mean the notification failed — check the destination directly.
Delivery Shows "Failed"
- Check the webhook URL is correct and accessible
- Verify the provider is not rejecting the request
- Review the error message in the delivery details