Overview
Guardian notifications keep your team informed about issues and events across all Guardian features. The notification system is designed to be flexible, allowing you to route different types of notifications to different channels based on service, environment, and other criteria.Notification Types
Guardian can send notifications for:| Feature | Notification Types |
|---|---|
| Deployments | New deployment events, deployment notifications |
| Deployment Verification | Verification results, issues detected |
| Anomaly Detection | Anomalies detected, investigation results |
| Investigations | New investigations, findings, recurring issues |
| Inbox | New actionable items, suggested fixes |
How Notification Routing Works
All Guardian features share a unified notification configuration system. For each feature, you can create multiple notification rules that specify:- Filter criteria - Which events trigger the notification
- Destination - Where to send the notification
Filter Criteria
Filter notifications by:- Service - Specific services or all services
- Environment - Specific environments (prod, staging, dev) or all
- Severity - Critical, high, medium, low (where applicable)
- Tags - Custom metadata tags on events
Example: Flexible Routing
You can create multiple configurations for the same feature: Deployment Notifications:- Config 1:
service-ainprod→#service-a-devs - Config 2: All services in
dev→#dev-deployments - Config 3:
payment-servicein any env →#payments-team
Setting Up Notifications
Step 1: Connect Notification Channels
Before configuring notifications, connect your notification channels:Step 2: Configure Feature Notifications
Each Guardian feature has its own notification settings:- Deployments
- Deployment Verification
- Anomaly Detection
- Inbox
Settings → Features → Deployment NotificationsConfigure notifications for new deployment events:
- Click Add Configuration
- Select services and environments to match
- Choose destination channel
- Save
Notification Channels
Slack
Slack is the recommended notification channel for Guardian. Notifications include:- Rich formatting with investigation details
- Direct links to Metoro for more information
- Action buttons where applicable
- Thread support for ongoing investigations
1
Connect Slack
Go to Settings → Integrations → Slack and authorize Metoro
2
Select Channels
Choose which Slack channels should receive notifications. You can select different channels for different notification configurations.
PagerDuty
For critical issues that require immediate attention:- Integrates with your existing PagerDuty escalation policies
- Map Guardian severity to PagerDuty urgency
- Create incidents automatically for critical issues
1
Connect PagerDuty
Go to Settings → Integrations → PagerDuty and enter your API key
2
Configure Services
Map Guardian notifications to PagerDuty services and set urgency levels
Webhooks
For custom integrations:- Send notifications to any HTTP endpoint
- Customize headers and payload format
- Integrate with internal tools or other services
1
Create Webhook
Go to Settings → Integrations → Webhooks and add your endpoint
2
Configure Payload
Define the request format and authentication
Notification Configuration Examples
Team-Based Routing
Route notifications to teams based on service ownership:Severity-Based Routing
Route based on severity or urgency:Environment-Based Routing
Different channels for different environments:Best Practices
Keep Production Focused
Route production notifications to dedicated channels that are actively monitored. Avoid mixing production and non-production alerts.Use Specific Channels
Create specific channels for specific purposes:#incidents- Critical issues requiring immediate action#deployments- Deployment notifications#service-alerts- Service-specific issues
Don’t Over-Notify
Configure notifications thoughtfully to avoid alert fatigue:- Not every event needs to go to every channel
- Use filtering to reduce noise
- Consider using digest notifications for non-urgent items
Route to the Right Teams
Ensure notifications reach people who can act on them:- Service issues → Team that owns the service
- Critical issues → On-call rotation
- General updates → Broader engineering channel
Troubleshooting
Not Receiving Notifications
- Check integration connection - Verify Slack/PagerDuty is connected in Settings → Integrations
- Check configuration - Ensure your notification configuration matches the events you expect
- Check channel permissions - Verify Metoro has permission to post to the channel
Too Many Notifications
- Review configurations - Look for overlapping or too-broad rules
- Add filters - Use service/environment filters to reduce scope
- Consolidate channels - Consider routing similar notifications together
Notifications Going to Wrong Channel
- Review rule order - Check which rules match your events
- Check filters - Verify service and environment filters are correct
- Test with specific service - Create a test configuration for one service
