incident.io

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 incident.io

1. Generate an Alerts configuration for groundcover Log in to your incident.io account. Go to "Alerts" -> "Configure"

1. Click on + "Add Alert Source"

1. On the alert source screen of the configuration the answer to the question "Where do your alerts come from?" should be "HTTP". Select this source and give it a unique name (e.g. groundcover). Hit "continue".

2. incident.io will create your configuration now, make sure to copy the Query authentication URL which you will need to use in the following steps in groundcover.

1. (Optional) It's recommended to configure the Connected App now in groundcover and wait with the completion on incident.io until an Alert has been sent so that incident.io can easily parse the attributes as they are received (this step can be reconfigured after creation as well).

Create an incident.io Connected App in groundcover

1. Go to: Settings -> Connected Apps

2. Click on incident.io

1. Select a name and paste the Alert Events URL (with the authentication inside)

2. (Optional) Add mapping for severity types, from groundcover to the custom severity types used in incident.io

1. Test the connection (Optional)

   • This will send a notification similar to the notification that will be sent by monitors with [TEST] Notification from groundcover in the title to differentiate from 'real' notifications.

2. Save

Controlling Auto-Resolution

By default, groundcover sends both "firing" and "resolved" states to incident.io, which auto-resolves alerts when monitors recover. If you want alerts to remain open until manually closed:

Option 1: Configure Notification Routes (Recommended)

1. Create a Notification Route with only "Firing" status (not "Resolved")

2. This prevents resolved notifications from being sent to incident.io

Option 2: Configure incident.io Configure your incident.io alert source to ignore resolved states or require manual resolution.

Payload Structure

The payload sent to incident.io 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) or custom mapped value configured in Connected App settings
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

Migrating from Workflows? incident.io Connected Apps use query authentication (token in URL), not bearer token authentication. The URL format should be the complete Alert Events URL provided by incident.io.