Rootly

This capability is only available to BYOC deployments. Check out our pricing page for more information about subscription plans and the available deployment modes.

Create an Alert Source in Rootly

1. Generate an Alerts configuration for groundcover Log in to your Rootly account. Go to "Alerts" -> "Sources"

1. Click on + "New Source" and search for Generic Webhook.

   
2. Add an 'Alert Source Name', e.g. 'groundcover' and optionally also Owning Teams, then click Add Source.

   
3. Choose your alert routing method.

4. Copy the Authorization Header Credentials. Click Continue.

   
5. (Optional) You can now send a test notification to see the payload that will be received from notifications.

   
6. Click Continue.

7. (Optional) Define severity mapping to Alert Urgency using $.metadata.severity

   
8. Important-

   1. Set the Unique Identifier: $.deduplication_key

   2. (Optional) Toggle on 'Combine duplicate alerts into one alert'

   3. Toggle On 'Auto-Resolve' and set:

      1. Field location: $.status

      2. Field value: resolved

         
9. Click 'Save changes'. You should not see your source.

   

Create a Rootly Destination in groundcover

1. Go to: Integrations → Destinations

2. Click on Rootly

   
3. Select a name and paste the API Key

1. (Optional) Test Connection- This will send a notification similar to the notification that will be send by monitors with [TEST] Notification from groundcover in the title to differentiate from 'real' notifications.

1. Save

Payload Structure

The payload sent to Rootly includes:

{
  "title": "{{ summary }}",
  "description": "{{ description }}",
  "status": "firing|resolved",
  "deduplication_key": "{{ fingerprint }}",
  "source_url": "{{ urls.issue }}",
  "metadata": {
    "severity": "{{ severity }}",
    "monitor_name": "{{ monitor_name }}",
    "monitor_id": "{{ monitor_id }}",
    "value": "{{ value }}",
    "threshold": "{{ threshold }}",
    "renotification_count": 0,
    "labels": {
      "cluster": "{{ labels.cluster }}",
      "namespace": "{{ labels.namespace }}",
      "workload": "{{ labels.workload }}"
    }
  }
}

This payload structure is fixed and cannot be customized. Values shown with {{ }} are dynamically populated from your monitor configuration. If you need a custom payload structure, use a Generic Webhook instead.

Test mode: When using "Test the connection", the status field will be "test" and other fields like value, threshold, and URLs may contain placeholder values.

Payload Field Reference

Field	Description
title	Issue title from the alert
description	Monitor description with variable expansion
status	Alert state: "firing", "resolved", or "test" (during connection testing)
deduplication_key	Alert fingerprint for grouping related alerts
source_url	Link to investigate the issue in groundcover
severity	Monitor severity (S1, S2, S3, S4)
monitor_name	Name of the monitor
monitor_id	Internal unique ID of the monitor
value	The value that triggered the alert
threshold	Configured threshold for the monitor
renotification_count	Counter for re-notifications (starts at 0)
labels	Monitor labels as key-value pairs. Only labels defined in the monitor's group-by or custom labels are included; keys may be absent if not defined