Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. Integrations
  2. Alerts integration
  • Getting Started
    • Introduction
    • Quick start
    • FAQ
    • Product Comparison
  • Incidents
    • What is an Incident
    • View Incidents
    • Handle Incidents
    • Escalations and Assignments
    • Custom Fields
    • Custom Actions
    • Alert Noise Reduction
    • Past Incidents
    • Outlier Incidents
  • Configure Flashduty
    • Channels
    • Integrate Alerts
    • Alert Noise Reduction
    • Escalation Rules
    • Label Enrichment
    • Schedules
    • Templates
    • Service Calendars
    • Preferences
    • Alert Routing
    • Silence and Inhibition
    • Filters
    • Notification Bots
    • Alert Pipeline
  • Platform
    • Teams and Members
    • Permissions
    • Single Sign-On
    • Insights
  • Advanced Features
    • Referencing Variables
    • Dynamic Assignment
  • Integrations
    • Alerts integration
      • Standard Alert Integration
      • Email Integration
      • Nightingale/FlashCat Integration
      • Prometheus Integration
      • Grafana Integration
      • Zabbix Integration
      • Uptime Kuma Integration
      • Alibaba Cloud ARMS Integration
      • Alibaba Cloud Monitor CM Event Integration
      • Alibaba Cloud Monitor CM Metrics Integration
      • Alibaba Cloud SLS Integration
      • AWS CloudWatch Integration
      • Azure Monitor Integration
      • Baidu Cloud BCM Integration
      • Huawei Cloud CES Integration
      • Influxdata Integration
      • Open Falcon Integration
      • PagerDuty Integration
      • Tencent BlueKing Integration
      • Tencent Cloud CLS Integration
      • Tencent Cloud Monitor CM Integration
      • Tencent Cloud EventBridge
      • OceanBase Integration
      • Graylog Integration
      • Skywalking Integration
      • Sentry Integration
      • Jiankongbao Integration
      • AWS EventBridge Integration
      • Dynatrace Integration
      • Huawei Cloud LTS Integration
      • GCP Integration
      • Splunk Alert Events Integration
      • AppDynamics Alert Integration
      • SolarWinds Alert Events Integration
      • Volcengine CM Alert Events Integration
      • Volcengine CM Event Center Integration
      • Volcengine TLS Integration
      • OpManager Integration
      • Meraki Integration
      • Keep Integration
      • ElastAlert2 Alert Integration
      • StateCloud Alert Events
      • Guance Alert Events
      • Zilliz Alert Events
      • Huawei Cloud APM Alerts
      • zstack integration
    • Change integration
      • Standard Change Event
      • Jira Issue Events
    • IM integration
      • Feishu (Lark) Integration Guide
      • Dingtalk Integration
      • WeCom Integration
      • Slack Integration
      • Microsoft Teams Integration
    • Single Sign-On
      • Authing Integration
      • Keycloak Guide
      • OpenLDAP Guide
    • Webhooks
      • Alert webhook
      • Incident webhook
      • Costom action
  • Terms
    • Terms of Service
    • User Agreement/Privary Policy
    • SLA
  1. Integrations
  2. Alerts integration

Keep Integration

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.
Expand
1.
Enter the Flashduty console, select Channel, and go to a specific channel's details page
2.
Select the Integrations tab, click Add Integration to enter the integration page
3.
Choose Keep integration, click Save to generate a card
4.
Click the generated card to view the Integration Key, copy it for later use, and you're done

Using Shared Integration#

Choose this method when you need to route alerts to different channels based on the alert event's payload information.
Expand
1.
Enter the Flashduty console, select Integration Center=>Alert Events to access the integration selection page
2.
Select Keep integration:
Integration Name: Define a name for this integration
3.
Configure default routing and select the corresponding channel (after the integration is created, you can go to Route to configure more routing rules)
4.
Click Save and copy the newly generated Integration Key for later use
5.
Done

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
修改于 2025-03-27 07:56:01
上一页
Meraki Integration
下一页
ElastAlert2 Alert Integration
Built with