Notification Routes

Notification Routes let you automatically send notifications to Connected Apps when monitor issues change state.

Creating and editing Notification Routes requires editor privileges in groundcover

How It Works

1. Scope: A gcQL query that filters which monitors' issues will trigger this route

2. Rules: Define what happens when an issue is in a specific state (Firing or Resolved)

3. Connected Apps: Choose where to send the notification (e.g., Slack Webhook, Pagerduty, etc)

Prerequisites

Before creating notification routes, set up your Connected Apps in Settings → Connected-Apps.

Create a Notification Route

1. Go to Monitors → Notification Routes

2. Click Create Notification Route

3. Complete the wizard:

Step 1: Route Name

Give your route a descriptive name (e.g., prod-critical-alerts, infra-team-notifications).

Step 2: Scope Monitors

Define which monitors this route applies to using gcQL on:

1. The grouping labels defined in the query

2. The custom labels

3. The Monitor's metadata such as the name or severity

Examples:

• env:prod — All monitors with grouping key 'env' and possible value of 'prod'

• env:prod AND severity:S1 — Only critical production alerts

• team:platform — Monitors with a custom label for the platform team

• *:* — To match all monitors

Step 3: Rules

Rules define what happens when a scoped monitor's issue changes state.

Each rule has:

• Status: When to trigger — Firing (issue is active) or Resolved (issue cleared)

• Connected Apps: Where to send the notification

Example setup:

• When Firing or Resolved → Send to #prod-alerts Slack channel

• When Firing (only) → Send to Pagerduty service directory

Click Add Rule to create multiple rules with different status/destination combinations.

Re-notification Interval

Configure how long to wait before sending another notification while an alert is still firing.

Options: 1m, 5m, 10m, 30m, 1h, 2h, 4h, 8h, 12h, 1d, 2d

This prevents notification fatigue from long-running alerts.

Managing Notification Routes

The Notification Routes page shows all your routes with:

• Name: Route identifier

• Scope: The gcQL query defining which monitors are affected

• Connected Apps: Summary of destinations by type

• Creator: Who created the route

Edit, Duplicate, or Delete

Hover over any row to access the action menu:

• Edit: Modify the route configuration

• Duplicate: Create a copy as a starting point

• Delete: Remove the route

Example Use Cases

Route Critical Production Alerts to PagerDuty and Slack

Name: prod-critical-pagerduty
Scope: env:prod AND severity:S1

Rules:
- When Firing → PagerDuty On-Call
- When Firing or Resolved → #critical-alerts (Slack)

Separate Routes by Team

Name: platform-team-alerts
Scope: team:platform

Rules:
- When Firing → #platform-alerts (Slack)
- When Resolved → #platform-alerts (Slack)

Name: backend-team-alerts
Scope: team:backend

Rules:
- When Firing → #backend-alerts (Slack)
- When Resolved → #backend-alerts (Slack)

Development Alerts — Firing Only

Name: dev-notifications
Scope: env:dev

Rules:
- When Firing → #dev-alerts (Slack)