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

In Flashduty

You can obtain an integration key through either of these 2 methods:

Using Dedicated Integration

Choose this method when you don’t need to route alert events to different channels - it’s simpler.

Using Shared Integration

Choose this method when you need to route alerts to different channels based on the alert event’s payload information.

In Keep


Field Definitions

FieldRequiredTypeDefinition
titleYesstringAlert title, maximum 512 characters, will be truncated if exceeded
event_statusYesstringAlert 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_keyNostringAlert 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
descriptionNostringAlert description, maximum 2048 characters, will be truncated if exceeded
labelsNomapAlert 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. Label content refers to Best Practices. Example: “resource”: “171.26.23.22”, “check”: “api latency > 500ms”

Configuration Method

Step 1: Configure Flashduty Provider

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

Step 2: Configure WorkFlows

  1. Login to Keep console, enter WorkFlows , create or edit an existing Workflow.
  2. Configure the Trigger section as needed.
  3. In the Steps section, select flashduty-action and select the Flashduty Provider configured in the previous step.
  4. 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).
  5. Click Save to save the configuration.
drawing