Auto-Resolution

Configure auto-resolution for the Generic Webhook Alert Source so Rootly can match recovery events to alerts using the identifiers and rules you define.

Overview

Auto-resolution allows Rootly to update alerts when your external system sends a recovery or resolved-style webhook event.

This is useful when your monitoring or observability platform sends one event when an issue starts and another when that issue clears. By configuring the correct identifier and state fields, Rootly can use those follow-up webhook events to recognize the related alert and apply the resolution logic you defined.

Before You Begin

Before configuring auto-resolution, make sure you already have a Generic Webhook Alert Source set up and that you understand which fields in your incoming webhook payload identify:

• The alert itself
• The current state of the alert

In most cases, you will need:

• An external identifier field that stays consistent across trigger and recovery events
• A state field that changes when the issue is resolved or cleared

If you have not configured those field mappings yet, start with the Installation page.

How It Works

Auto-resolution depends on the resolution configuration stored on the source.

For the Generic Webhook Alert Source, that configuration is based on:

• The field that identifies the alert
• The field that represents its state
• The value that should be treated as resolved

These settings allow Rootly to handle follow-up webhook events consistently when your source sends a recovery or cleared event.

Configure Auto-Resolution

1. Map the identifier field

   Configure a field mapping for the external identifier in your webhook payload.

   This value should stay consistent across events for the same alert so Rootly can associate follow-up webhook events with the correct alert.

2. Map the state field

   Configure a field mapping for the alert state in your webhook payload.

   This field should represent whether the alert is active, cleared, resolved, or in another lifecycle state used by your source system.

3. Define the resolved state value

   Set the state value that Rootly should treat as resolved.

   In most cases, this is an exact match against the value you configure, such as resolved, recovered, or ok.

4. Enable auto-resolution

   Turn on auto-resolution for the Generic Webhook Alert Source after your identifier and state mappings are configured.

   Once enabled, Rootly uses those mappings and the resolved-state value as part of the source’s resolution configuration.

Important Notes

• Auto-resolution depends on the field mappings configured for the source
• The identifier field and state field should be stable and predictable in your incoming webhook payload
• If your payload does not include the expected values, Rootly may still ingest the alert event, but it may not resolve the alert the way you intend
• Some teams may also use payload-driven alert status fields separately from auto-resolution mapping
• Teams using newer alert field or resolution-rule configuration may manage this behavior through that newer configuration path instead of the legacy generic webhook mapping flow

Related Configuration

Auto-resolution is closely related to your webhook field mappings and alert automation setup.

Installation

Set up the source, configure authentication, and map the incoming webhook payload fields.

Alert Workflows

Automate incident creation, notifications, and other alert-driven actions after alerts are received.