Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. Configure Flashduty
  • 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
    • Data Security
  1. Configure Flashduty

Alert Routing

When receiving alerts through shared integrations, you can configure routing rules to distribute alerts of the same type or related business to corresponding channels for classified processing and analysis.

Configuration Steps#


Configuration path: Integration Center => Alert Events => Select Integration Details => Routes => Add Route
1. Add Routes: Multiple routes can be added without current limitations, but it's recommended to keep them simple as too many rules may reduce readability.
2. Adjust Order: When there are two or more routing rules, you can adjust their execution order using up and down arrows.
3. Routing Rules: Supports multiple conditions and rules with logical operations (including match or non-match operations). Various matching modes are available, such as exact match, wildcard, and regex. You can visit Configure Filter Conditions to learn how to set up conditions.
4. Flow Control: When there are multiple routing rules, you can choose to stop or continue matching subsequent rules. The default is continue matching, meaning lower routes remain effective. Selecting stop will prevent lower rules from taking effect.
5. Preview Rules: After configuration, you can review the rule expressions.
6. Insert Routes: With multiple routing rules, you can insert new routes before or after existing ones, eliminating the need to adjust order manually.
7. Default Route: Shared integrations require at least one routing rule to receive alerts. A default routing rule is provided to distribute alerts to corresponding channels when no rules are configured or matched.
8. Target Channels: You can select multiple channels to receive matched alerts.
drawing

Configuration Example#


Distribute Same Business Group to One Channel#

Scenario: Route alerts from the same business group in FlashCat monitoring platform to a unified channel.
Rule: Match based on Labels.group_name tag.
drawing

FAQ#


Why aren't routing rules taking effect?
Please verify if the alerts match the rules and if the rules are configured correctly.
What happens when multiple identical routing rules deliver to the same channel?
An incident will be generated for each channel. It's recommended to select multiple channels within the same rule instead.
Why am I not receiving alerts after configuring routing rules?
Please verify if incoming alerts match your configured routing rules. It's recommended to set up a default fallback route to catch unmatched alerts.
When flow control is set to stop, will the default route still match?
Yes, the default route serves as a fallback and is not affected by flow control settings.
修改于 2024-12-11 02:39:01
上一页
Preferences
下一页
Silence and Inhibition
Built with