Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. Alerts integration
  • Introduction
  • On-call
    • Getting Started
      • 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 On-call
      • 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
    • Advanced Features
      • Referencing Variables
      • Dynamic Assignment
      • Insights
    • 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
  • RUM
    • Getting Started
      • Introduction
      • Quick start
      • FAQ
    • Applications
      • Applications
      • SDK Integration
      • Advanced Configuration
      • Analysis Dashboard
    • Performance Monitoring
      • Overview
      • Metrics
      • Performance Analysis
      • Performance Optimize
    • Error Tracking
      • Overview
      • Error Reporting
      • Issues
      • Source Mapping
      • Error Grouping
      • Issue States
      • Issue Alerting
    • Others
      • Terminology
      • Data Collection
      • Data Security
  • Platform
    • Teams and Members
    • Permissions
    • Single Sign-On
  • Terms
    • Terms of Service
    • User Agreement/Privary Policy
    • SLA
    • Data Security
  1. Alerts integration

Grafana Integration

Sync Grafana alert events to Flashduty via webhook to achieve automated alert noise reduction.

In Flashduty#

You can obtain an integration push URL through either of these two methods:

Using Private Integration#

Choose this method when you don't need to route alert events to different channels. It's simpler.
Expand
1.
Go to Flashduty console, select Channel, and enter a channel's details page
2.
Select the Integrations tab, click Add Integration to enter the integration page
3.
Choose Grafana integration and click Save to generate a card
4.
Click the generated card to view the push URL, 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.
Go to Flashduty console, select Integration Center=>Alert Events to enter the integration selection page
2.
Select Grafana integration:
Integration Name: Define a name for this integration
3.
Configure the default route 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 push URL for later use
5.
Done

In Grafana#

Grafana V4~V8 versions enable Legacy Alerting by default, while V9 and later versions enable Grafana Alerting by default. For feature distinctions and activation methods, please refer to the official documentation. Follow these steps based on your deployed version.

Legacy Alerting#

1.
Open your Grafana console and navigate to Alerting > Notification channels
2.
Click Add Channel to open the channel configuration dialog
3.
Configure the name, select webhook as Type, enter the integration push URL in the Url field, and select POST as Method, as shown below:
drawing
4.
Save and return to the integration list. After an alert occurs, if the latest event time is displayed, the configuration is successful and events are being received
5.
Complete

Grafana Alerting#

1.
Open your Grafana console and navigate to Alerting > Contact points
2.
Click New contact point to open the configuration dialog
3.
Configure the name, select webhook as Type, enter the integration push URL in the Url field, and select POST as Method, as shown below:
drawing
4.
Open the Notification policies page, edit or add a policy as needed, and select the contact point created in the previous step as the delivery channel, as shown below:
drawing
5.
Save and return to the integration list. After an alert occurs, if the latest event time is displayed, the configuration is successful and events are being received
6.
The default alert severity is warning. To customize it, you can configure the severity label in the alert details page (refer to the status mapping below), as shown in the following image:
drawing
7.
Complete

Status Mapping#

Legacy Alerting to Flashduty severity mapping:
Legacy AlertingFlashdutyStatus
alertingWarningWarning
no_dataCriticalCritical
okOkResolved
Grafana Alerting to Flashduty severity mapping:
The system extracts the severity, priority, and level labels from alert events in sequence. The corresponding value will be used as Prometheus's own alert severity. If none are found, the system automatically sets the Prometheus alert severity to warning.
Grafana AlertingFlashdutyStatus
criticalCriticalCritical
warningWarningWarning
warnWarningWarning
infoInfoInfo
acknowledgedInfoInfo
unknownInfoInfo
unkInfoInfo
okOkResolved

添加官方技术支持微信

在这里，获得使用上的任何帮助，快速上手FlashDuty

微信扫码交流
上一页
Prometheus Integration
下一页
Zabbix Integration
Built with