Notification Settings - Metoro Documentation

Overview

AI SRE notifications keep your team informed about issues and events across all AI SRE workflows. 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

Metoro 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

How Notification Routing Works

All AI SRE workflows 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-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:

Slack

Connect Slack workspace

Webhooks

Configure webhooks

Email needs no setup — you enter recipient addresses directly when choosing it as a destination.

Step 2: Configure Feature Notifications

Each AI SRE workflow has its own notification settings:

Deployments
Deployment Verification
Anomaly Detection
Issues

Settings → Features → Deployment NotificationsConfigure notifications for new deployment events:

Click Add Configuration
Select services and environments to match
Choose destination channel
Save

Learn more →

Settings → Features → Issue NotificationsConfigure notifications for newly created issues:

Click Add Configuration
Optionally leave the filter blank, or use eventType == "issue_created"
Choose destination
Save

Learn more →

Notification Channels

Slack

Slack is the recommended notification channel for AI SRE workflows. Notifications include:

Rich formatting with investigation details
Direct links to Metoro for more information
Action buttons where applicable
Thread support for ongoing investigations

Connect Slack

Go to Settings → Integrations → Slack and authorize Metoro

Select Channels

Choose which Slack channels should receive notifications. You can select different channels for different notification configurations.

Email

Send notifications straight to one or more email addresses — no integration setup required, just enter the recipient addresses when selecting Email as the destination. Email is available for the notification types where a self-contained summary makes sense:

Deployment verification completed (verdict with summary)
Investigation completed (findings summary)
Issue created

Other notification types (deployment detected, verification scheduled/started, anomaly detected, agent action approvals) support Slack and webhook destinations only.

PagerDuty is available as a destination for alerts, but not for AI SRE notifications.

Webhooks

For custom integrations. Webhook destinations can be selected in all AI SRE notification settings: deployment monitoring, autonomous investigations, issue notifications, and agent action approvals.

Send notifications to any HTTP endpoint
Customize headers and payload format via webhook templates
Integrate with internal tools or other services

If you don’t define a custom body template on the webhook integration, Metoro sends a structured JSON event of this shape:

{
  "id": "5f6e0c62-4f19-4a1d-9c62-0b1f3d1a9e01",
  "type": "deploymentRolloutDetected",
  "timestamp": "2026-07-29T12:00:00Z",
  "title": "Deployment payments (https://app.metoro.io/...) updated in namespace `prod`",
  "message": "...",
  "data": {
    "deepLink": "https://app.metoro.io/service?service=payments",
    "serviceName": "payments",
    "environment": "production",
    "namespace": "prod",
    "resourceName": "payments",
    "resourceKind": "Deployment",
    "isNewWorkload": false,
    "changeType": "image",
    "imageChanges": [
      { "container": "payments", "previousImage": "repo/payments:v1", "newImage": "repo/payments:v2" }
    ]
  }
}

The title and message fields are plain text — Slack-specific markup is stripped and links are rendered as label (url). The id field is the UUID of the underlying event (stable across delivery retries — use it for deduplication), and type identifies the specific event so you can filter on your end. The data object is typed per event type and includes a deepLink into the Metoro UI (all event types except deploymentVerificationScheduled, where no verification page exists yet); its full schema for every event type is documented in the Webhook Events section of the API reference (starting at deployment rollout detected). For custom body templates, see webhook template variables for the variables each event type provides.

Create Webhook

Go to Settings → Integrations → Webhooks and add your endpoint

Configure Payload

Define the request format and authentication

Select the Webhook as a Destination

In any AI SRE notification settings page, add or edit a configuration and choose Webhook as the destination type, then pick your webhook

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

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

Check integration connection - Verify Slack is connected (or your webhook is configured) 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

Slack Integration

Complete Slack setup guide

Webhooks

Custom webhook setup

AI SRE Overview

Learn how AI SRE fits into Metoro’s broader platform

​Overview

​Notification Types

​How Notification Routing Works

​Filter Criteria

​Example: Flexible Routing

​Setting Up Notifications

​Step 1: Connect Notification Channels

Slack

Webhooks

​Step 2: Configure Feature Notifications

​Notification Channels

​Slack

​Email

​Webhooks

​Notification Configuration Examples

​Team-Based Routing

​Severity-Based Routing

​Environment-Based Routing

​Best Practices

​Keep Production Focused

​Use Specific Channels

​Don’t Over-Notify

​Route to the Right Teams

​Troubleshooting

​Not Receiving Notifications

​Too Many Notifications

​Notifications Going to Wrong Channel

​Related Documentation

Slack Integration

Webhooks

AI SRE Overview

Overview

Notification Types

How Notification Routing Works

Filter Criteria

Example: Flexible Routing

Setting Up Notifications

Step 1: Connect Notification Channels

Step 2: Configure Feature Notifications

Notification Channels

Slack

Email

Webhooks

Notification Configuration Examples

Team-Based Routing

Severity-Based Routing

Environment-Based Routing

Best Practices

Keep Production Focused

Use Specific Channels

Don’t Over-Notify

Route to the Right Teams

Troubleshooting

Not Receiving Notifications

Too Many Notifications

Notifications Going to Wrong Channel

Related Documentation