Notification Channels
Notification channels define where Rime sends alerts when an alert rule fires. You can configure multiple channels and assign them to different rules or escalation policies. Each channel type has its own configuration requirements and message format.
Channel types
Email notifications are sent via SMTP. You can use your own mail server or a service like SendGrid, Amazon SES, or Microsoft 365.
Configuration fields:
| Field | Description |
|---|---|
| SMTP host | The mail server hostname (e.g., smtp.sendgrid.net) |
| SMTP port | Usually 587 (STARTTLS) or 465 (SSL/TLS) |
| Username | SMTP authentication username |
| Password | SMTP authentication password (stored encrypted) |
| From address | The sender address for alert emails |
| Recipients | One or more email addresses that receive the alerts |
Message format: Alert emails include the rule name, severity, resource details, the current metric value, the threshold that was breached, and a link to the alert in the Rime dashboard. The email template is not customizable in the current release.
Slack
Slack notifications are sent via incoming webhooks. Each channel maps to one Slack webhook URL.
Configuration fields:
| Field | Description |
|---|---|
| Webhook URL | The Slack incoming webhook URL for the target channel |
| Channel override | Optional. Overrides the channel set in the webhook configuration |
| Username | Optional. The display name for the bot posting the message |
Message format: Slack messages use block formatting with color-coded severity indicators (red for critical, orange for warning, grey for info). The message includes the rule name, affected resource, current value, and a link to the alert detail page.
To create a webhook URL, go to your Slack workspace’s app management page, create an incoming webhook, and copy the URL into Rime.
PagerDuty
PagerDuty integration sends events through the PagerDuty Events API v2. Alerts map to PagerDuty incidents based on severity.
Configuration fields:
| Field | Description |
|---|---|
| Integration key | The PagerDuty integration key (also called routing key) from your PagerDuty service |
| Severity mapping | How Rime severities map to PagerDuty severities |
Default severity mapping:
| Rime severity | PagerDuty severity |
|---|---|
| Critical | Critical |
| Warning | Warning |
| Info | Info |
You can override this mapping if your PagerDuty escalation policies use different severity levels.
When an alert is resolved in Rime, a resolve event is automatically sent to PagerDuty to close the corresponding incident.
Webhooks
Custom webhooks send alert data as JSON to any HTTP endpoint. Use this for integrations with systems that Rime does not have a built-in channel for (Microsoft Teams, Opsgenie, custom internal tools).
Configuration fields:
| Field | Description |
|---|---|
| URL | The HTTP endpoint to POST to |
| Headers | Optional. Custom headers to include in the request (e.g., API keys, content type overrides) |
| Payload template | Optional. A custom JSON template for the request body. If omitted, Rime sends its default alert payload |
Default payload:
{ "alert_id": "uuid", "rule_name": "Snowpipe delay > 15m", "severity": "warning", "status": "firing", "resource_type": "snowpipe", "resource_id": "uuid", "resource_name": "raw_ingestion_pipe", "current_value": "18", "threshold": "15", "fired_at": "2026-03-05T10:30:00Z", "dashboard_url": "https://{tenant}.rimedata.io/monitoring/alerts/uuid"}Payload template variables: If you provide a custom payload template, you can use the following variables: {{alert_id}}, {{rule_name}}, {{severity}}, {{status}}, {{resource_type}}, {{resource_id}}, {{resource_name}}, {{current_value}}, {{threshold}}, {{fired_at}}, {{dashboard_url}}.
Rime expects the webhook endpoint to return a 2xx status code. Non-2xx responses are logged as delivery failures and retried up to three times with exponential backoff.
Channel availability by tier
Not all channel types are available on every licensing tier:
| Tier | Available channels |
|---|---|
| Free / Trial | Email only |
| Small Business | Email, Slack |
| Business | Email, Slack, PagerDuty, Webhooks |
| Business Critical | Email, Slack, PagerDuty, Webhooks |
If you attempt to configure a channel type that your tier does not support, the UI displays a message prompting you to upgrade. See Licensing for full tier details.
Testing a channel
After configuring a channel, use the Send Test Notification button to verify it works. The test sends a sample alert through the channel with placeholder data. This confirms:
- Network connectivity between Rime and the target system
- Authentication credentials are valid
- The message arrives in the expected format and location
You should always test a channel before assigning it to an alert rule or escalation policy. A channel that has never been tested displays a warning badge in the channel list.
Channel groups
You can create a channel group to send the same alert to multiple channels at once. For example, you might create a “Critical incidents” group that includes both a PagerDuty channel and a Slack channel, so critical alerts page the on-call engineer and notify the team channel simultaneously.
To create a group, navigate to Monitoring > Notification Channels > Create Group, give it a name, and select the channels to include. You can then assign the group to alert rules or escalation policies the same way you would assign an individual channel.
Credential security
All channel credentials (SMTP passwords, webhook URLs, PagerDuty integration keys) are encrypted at rest using AES-256-GCM, the same encryption used for connector credentials. Credentials are decrypted only at the moment a notification is sent.
Next steps
- Set up escalation policies to define what happens when alerts are not acknowledged
- Review alert rules to control what triggers notifications
- See Licensing for details on channel availability by tier