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

Outlier Incidents

Identify whether incidents are common or Outlier to expedite incident handling.

A Outlier incident is one that has not occurred within a specific past time period. When an incident is identified as Outlier, incident responders should be particularly vigilant. This is crucial for OnCall engineers, as the impact of Outlier incidents may be unknown, and response procedures might require ad-hoc decisions. Some engineers may specifically focus on these Outlier incidents to establish standardized procedures or SOPs for handling them.
提示
This feature is currently in beta and is only available in Professional and higher subscription plans. Please contact us if you need to activate this feature.

Viewing Outlier Incidents#


Console#

1.
In the incident list page, Outlier incidents will be clearly marked with a Outlier indicator;
2.
In the incident details page, Outlier incidents will display a prominent Outlier indicator and explanation at the top.
drawing

IM Tools#

Taking Feishu/Lark as an example, when an incident is identified as Outlier, the system will enhance the notification:
drawing

How It Works#

The system uses machine learning models to determine the similarity between incidents. When the similarity is greater than 90%, we consider two incidents to be similar.
When determining similarity, we primarily consider the following factors:
1.
Incident title
2.
Incident detailed description
3.
Affected services (typically extracted from service labels)
4.
Alert objects within the incident (typically extracted from resource labels)
When the system detects that no similar incidents have occurred in the past 30 days, it marks the incident as Outlier.

FAQ#


Does the Outlier incident feature need to be enabled separately?
No setup or activation is required. Outlier incident identification is automatically enabled for all Professional and higher subscription plans.
修改于 2024-11-25 03:39:43
上一页
Past Incidents
下一页
Channels
Built with