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

Past Incidents

Review similar historical incident resolutions to quickly handle new incidents.

When responding to incidents, having access to historical solutions for similar incidents can significantly speed up the resolution process. The Past Incidents feature provides responders with a list of resolved similar incidents. For responders unfamiliar with the issue, they can quickly review the timeline, root cause, and resolution of historical incidents, and replicate relevant actions. Past incidents provide the necessary context for problem-solving and help prevent panic when responders encounter unfamiliar issues.
提示
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.

View Similar Incidents#


Console#

1.
From the incident list or channel, locate an incident that needs attention;
2.
Click the incident title to enter the incident details, then select the Past Incidents tab.
drawing
The system will show up to 5 similar historical incidents to avoid overwhelming you with too much information.

Sorting Principles#

How do we sort the results?
1.
The system only matches incidents with similarity above 90%;
2.
The system prioritizes incidents with more detailed resolutions and root causes;
3.
The system prioritizes incidents with higher similarity;
4.
The system prioritizes more recent incidents.
提示
It's good practice to document the resolution and root cause each time you resolve an incident, as this greatly improves the response speed for future responders.

How We Identify Similarities#

The system uses machine learning models to determine the similarity between incidents. When the similarity is above 90%, we consider two incidents to be similar.
When determining similarity, we mainly consider these factors:
1.
Incident title
2.
Incident description
3.
Affected services (usually extracted from service labels)
4.
Alert objects involved (usually extracted from resource labels)
When searching for historical incidents, the system only matches resolved similar incidents within the current channel.

FAQ#


How far back can I view historical incidents?
Currently, you can only view similar incidents from the 30 days prior to the current incident. As time passes, the system may delete historical data, in which case you may not be able to view past incidents.
Regardless, for currently occurring incidents, you can access up to 30 days of historical data.
Can I mark current incidents as not similar to historical ones?
No, the system currently doesn't have this marking feature. However, you can communicate and provide feedback through other channels.
How can I improve the effectiveness of historical incidents?
1.
We recommend completing the root cause and resolution fields for important incidents;
2.
We recommend enriching incident labels, especially service and resource labels;
3.
We recommend providing detailed alert titles and descriptions that accurately express the incident symptoms.
修改于 2024-11-25 03:39:32
上一页
Alert Noise Reduction
下一页
Outlier Incidents
Built with