Notifications

Configure multi-channel notifications for incidents, maintenances, and alerts.

Overview

ReliaPulse supports multiple notification channels:

• Email - SMTP email notifications
• SMS - Text message alerts
• Slack - Slack workspace messages
• Discord - Discord channel webhooks
• Microsoft Teams - Teams channel connectors
• Webhooks - Custom HTTP endpoints

Notification Channels

Setting Up Channels

1. Navigate to Settings > Notifications
2. Click "Add Channel"
3. Select channel type
4. Configure settings
5. Test the connection
6. Save

Email

Send notifications via SMTP:

Testing:

# Test email configuration
curl -X POST http://localhost:3000/api/v1/notification-channels/{id}/test \
  -H "Authorization: Bearer sk_live_xxx"

Slack

Send messages to Slack channels:

1. Create a Slack App or use incoming webhooks
2. Get the webhook URL
3. Configure in ReliaPulse:

Message format:

• Rich formatting with status colors
• Component and incident details
• Action buttons (if app configured)

Discord

Send messages to Discord channels:

1. Go to channel settings → Integrations → Webhooks
2. Create a webhook and copy the URL
3. Configure:

Message format:

• Embedded messages with colors
• Status icons
• Timestamp and details

Microsoft Teams

Send cards to Teams channels:

1. In Teams, go to channel → Connectors
2. Add "Incoming Webhook"
3. Configure and copy the URL
4. Add to ReliaPulse:

Message format:

• Adaptive cards
• Action buttons
• Status indicators

SMS

Send text messages via Twilio:

Custom Webhooks

Send data to any HTTP endpoint:

Payload template variables:

{
  "type": "{{event_type}}",
  "incident": {
    "id": "{{incident.id}}",
    "title": "{{incident.title}}",
    "status": "{{incident.status}}"
  },
  "timestamp": "{{timestamp}}"
}

Notification Events

Incident Events

Maintenance Events

Monitor Events

Channel Configuration

Event Filtering

Choose which events trigger notifications:

1. Edit the channel
2. Under "Events", select events to notify
3. Save

Component Filtering

Limit notifications to specific components:

1. Edit the channel
2. Under "Components", select which components
3. Leave empty for all components

Impact Filtering

Filter by incident severity:

• Minor incidents
• Major incidents
• Critical incidents only

Notification Templates

Customize notification content:

Email Templates

1. Navigate to Settings > Email Branding
2. Customize:
   • Logo
   • Colors
   • Header/Footer text
   • Custom CSS

Message Templates

Create templates for consistent messaging:

Subject: [{{status}}] {{title}}

Status: {{status}}
Impact: {{impact}}
Components: {{components}}

{{message}}

View details: {{url}}

Testing Notifications

Test Button

1. Open a notification channel
2. Click "Send Test"
3. Verify receipt

Test Incident

1. Create a test incident
2. Mark as test/internal
3. Verify notifications
4. Delete the incident

Subscriber Notifications

Subscribers receive notifications based on their preferences:

See Subscribers for details.

Rate Limiting

Prevent notification spam:

API Access

List Channels

curl http://localhost:3000/api/v1/notification-channels \
  -H "Authorization: Bearer sk_live_xxx"

Create Channel

curl -X POST http://localhost:3000/api/v1/notification-channels \
  -H "Authorization: Bearer sk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Slack Engineering",
    "type": "slack",
    "config": {
      "webhookUrl": "https://hooks.slack.com/xxx"
    },
    "events": ["incident.created", "incident.updated", "incident.resolved"]
  }'

Test Channel

curl -X POST http://localhost:3000/api/v1/notification-channels/{id}/test \
  -H "Authorization: Bearer sk_live_xxx"

Troubleshooting

Notifications Not Sending

1. Check channel is enabled
2. Verify event is selected
3. Check component filter
4. Review notification logs
5. Test the channel

Delayed Notifications

1. Check worker is running
2. Review Redis connection
3. Check queue backlog
4. Monitor worker logs

Wrong Recipients

1. Verify subscriber settings
2. Check component filters
3. Review notification rules

Best Practices

Channel Organization

• Create channels per team/purpose
• Use descriptive names
• Document notification purpose

Event Selection

• Start with critical events only
• Add more as needed
• Avoid notification fatigue

Testing

• Test after any configuration change
• Use test incidents regularly
• Verify all channels periodically

Related Documentation

• Subscribers - User subscriptions
• On-Call - Alert escalation
• Incidents - Incident notifications