> ## Documentation Index
> Fetch the complete documentation index at: https://metoro.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Notification Settings

> Configure flexible notification routing for all AI SRE features

## 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:

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:

<CardGroup cols={3}>
  <Card title="Slack" icon="slack" href="/integrations/slack">
    Connect Slack workspace
  </Card>

  <Card title="PagerDuty" icon="pager" href="/integrations/pagerduty">
    Connect PagerDuty
  </Card>

  <Card title="Webhooks" icon="webhook" href="/integrations/webhooks">
    Configure webhooks
  </Card>
</CardGroup>

### Step 2: Configure Feature Notifications

Each AI SRE workflow has its own notification settings:

<Tabs>
  <Tab title="Deployments">
    **Settings** → **Features** → **Deployment Notifications**

    Configure notifications for new deployment events:

    1. Click **Add Configuration**
    2. Select services and environments to match
    3. Choose destination channel
    4. Save

    [Learn more →](/ai-sre/deployment-verification)
  </Tab>

  <Tab title="Deployment Verification">
    **Settings** → **Features** → **Deployment Verification**

    Configure notifications for verification results:

    1. Click **Add Notification Configuration**
    2. Select services and environments
    3. Choose destination for verification alerts
    4. Save

    [Learn more →](/ai-sre/deployment-verification)
  </Tab>

  <Tab title="Anomaly Detection">
    **Settings** → **Features** → **Anomaly Detection**

    Configure notifications for detected anomalies:

    1. Click **Add Notification Configuration**
    2. Select services and environments to monitor
    3. Choose destination channel
    4. Save

    [Learn more →](/ai-sre/anomaly-detection)
  </Tab>

  <Tab title="Issues">
    **Settings** → **Features** → **Issue Notifications**

    Configure notifications for newly created issues:

    1. Click **Add Configuration**
    2. Optionally leave the filter blank, or use `eventType == "issue_created"`
    3. Choose destination
    4. Save

    [Learn more →](/ai-sre/issues)
  </Tab>
</Tabs>

## 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

<Steps>
  <Step title="Connect Slack">
    Go to **Settings** → **Integrations** → **Slack** and authorize Metoro
  </Step>

  <Step title="Select Channels">
    Choose which Slack channels should receive notifications. You can select different channels for different notification configurations.
  </Step>
</Steps>

### PagerDuty

For critical issues that require immediate attention:

* Integrates with your existing PagerDuty escalation policies
* Map AI SRE severity to PagerDuty urgency
* Create incidents automatically for critical issues

<Steps>
  <Step title="Connect PagerDuty">
    Go to **Settings** → **Integrations** → **PagerDuty** and enter your API key
  </Step>

  <Step title="Configure Services">
    Map AI SRE notifications to PagerDuty services and set urgency levels
  </Step>
</Steps>

### Webhooks

For custom integrations:

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

<Steps>
  <Step title="Create Webhook">
    Go to **Settings** → **Integrations** → **Webhooks** and add your endpoint
  </Step>

  <Step title="Configure Payload">
    Define the request format and authentication
  </Step>
</Steps>

## 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

## Related Documentation

<CardGroup cols={2}>
  <Card title="Slack Integration" icon="slack" href="/integrations/slack">
    Complete Slack setup guide
  </Card>

  <Card title="PagerDuty Integration" icon="pager" href="/integrations/pagerduty">
    PagerDuty configuration
  </Card>

  <Card title="Webhooks" icon="webhook" href="/integrations/webhooks">
    Custom webhook setup
  </Card>

  <Card title="AI SRE Overview" icon="brain" href="/ai-sre/overview">
    Learn how AI SRE fits into Metoro's broader platform
  </Card>
</CardGroup>