Skip to main content

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:
FeatureNotification Types
DeploymentsNew deployment events, deployment notifications
Deployment VerificationVerification results, issues detected
Anomaly DetectionAnomalies detected, investigation results
InvestigationsNew investigations, findings, recurring issues
InboxNew 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:
  1. Filter criteria - Which events trigger the notification
  2. 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-a in prod#service-a-devs
  • Config 2: All services in dev#dev-deployments
  • Config 3: payment-service in any env → #payments-team
This ensures the right people get notified about the right events.

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:
SettingsFeaturesDeployment NotificationsConfigure notifications for new deployment events:
  1. Click Add Configuration
  2. Select services and environments to match
  3. Choose destination channel
  4. Save
Learn more →

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 SettingsIntegrationsSlack 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 SettingsIntegrationsPagerDuty 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 SettingsIntegrationsWebhooks 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:
Payment Services:
- Services: payment-api, checkout-service, billing-service
- Environments: prod
- Destination: #payments-team

Platform Services:
- Services: api-gateway, auth-service
- Environments: prod
- Destination: #platform-team

All Staging:
- Services: All
- Environments: staging
- Destination: #staging-alerts

Severity-Based Routing

Route based on severity or urgency:
Critical Issues:
- Filter: severity = critical
- Destination: #incidents (with PagerDuty)

Non-Critical:
- Filter: severity != critical
- Destination: #engineering-alerts

Environment-Based Routing

Different channels for different environments:
Production:
- Environments: prod
- Destination: #production-alerts

Development:
- Environments: dev, staging
- Destination: #dev-notifications

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

  1. Check integration connection - Verify Slack/PagerDuty is connected in Settings → Integrations
  2. Check configuration - Ensure your notification configuration matches the events you expect
  3. Check channel permissions - Verify Metoro has permission to post to the channel

Too Many Notifications

  1. Review configurations - Look for overlapping or too-broad rules
  2. Add filters - Use service/environment filters to reduce scope
  3. Consolidate channels - Consider routing similar notifications together

Notifications Going to Wrong Channel

  1. Review rule order - Check which rules match your events
  2. Check filters - Verify service and environment filters are correct
  3. Test with specific service - Create a test configuration for one service