View Similar Incidents
Console

Ranking Principle
How do we rank them?- System only matches incidents with similarity greater than 90%
- System prioritizes incidents with more detailed resolutions and root causes
- System prioritizes incidents with higher similarity
- System prioritizes more recently occurred incidents
Recognition Method
The system uses machine learning models to determine similarity between incidents. When similarity exceeds 90%, we consider two incidents similar. When judging similarity, we mainly consider these factors:| Factor | Description |
|---|---|
| Incident Title | Semantic similarity of title text |
| Incident Description | Semantic similarity of description content |
| Affected Service | Generally extracted from service label |
| Alert Resources in Incident | Generally extracted from resource label |
When searching past incidents, the system only matches similar resolved incidents within the current channel.
FAQ
How far back can I view past incidents?
How far back can I view past incidents?
Currently, you can only view similar incidents within 30 days before the current incident occurred. 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 review up to 30 days of historical data.
Can I mark that current and past incidents are not similar?
Can I mark that current and past incidents are not similar?
No, the system currently has no marking feature. But you can communicate and provide feedback through other channels.
How can I make past incidents more effective?
How can I make past incidents more effective?
- We recommend filling in complete root cause and resolution for important incidents
- We recommend enriching incident labels, especially
serviceandresourcelabels - We recommend enriching alert titles and descriptions to more accurately express incident symptoms