Keep Alert Integration Guide

Push alert events to Flashduty through Keep’s Flashduty Provider to achieve automated alert noise reduction.

In Keep

Field	Required	Type	Definition
title	Yes	string	Alert title, maximum `512` characters, will be truncated if exceeded
event_status	Yes	string	Alert status. Enumerated values (`First letter capitalized`): Critical: Critical, Warning: Warning, Info: Info, Ok: Recovery. When set to Ok, it indicates automatic recovery of the alert
alert_key	No	string	Alert identifier, used for updating or automatically recovering existing alerts. You can customize this value, but it cannot exceed `255` characters. You can also rely on system-generated values, which will be returned in the response. This value must exist if you’re reporting a recovery event
description	No	string	Alert description, maximum `2048` characters, will be truncated if exceeded
labels	No	map	Alert label collection, where key is the label name and value is the label value. 1. Both label key and value are case-sensitive strings. 2. Label keys should not exceed `128` characters and follow Prometheus label naming conventions. Values should not exceed `2048` characters, will be truncated if exceeded. 3. Maximum `50` labels allowed. See Standard Alert Best Practices. Example: “resource”: “171.26.23.22”, “check”: “api latency > 500ms”

Login to Keep console, enter Providers list, select and click Flashduty.
Fill in the Flashduty Integration Key field with the Integration Key of Flashduty.
Click Save to save the configuration.

Login to Keep console, enter WorkFlows , create or edit an existing Workflow.
Configure the Trigger section as needed.
In the Steps section, select flashduty-action and select the Flashduty Provider configured in the previous step.
In the flashduty-action’s Configure section, configure the alert title, alert status, alert description, and alert labels (for details on the field definitions, please refer to Field Definitions).
Click Save to save the configuration.