Critical alerts are designed to flag high-priority issues that require immediate attention, helping you focus on anomalies that could have a significant impact on your operations.
When is an alert marked as critical?
An alert is marked as critical when either of the following conditions are met:
-
Repeated Anomaly
- The same anomaly has been detected before.
- This indicates that the issue is not a one-time deviation but a recurring or persistent problem that could signal an ongoing risk.
-
Threshold Breach
- The anomaly exceeds a predefined threshold value of 7.
- This ensures that only anomalies of significant magnitude or frequency are flagged as critical, preventing over-notification for minor deviations.
By combining these two conditions, critical alerts highlight patterns that are both consistent and impactful, ensuring a focus on actionable insights.
For example:
- If an anomaly in customer complaint volume is detected repeatedly over several days or surpasses a volume threshold of 7, it would be flagged as critical.
- Similarly, if an operational metric continues to deviate in the same direction (e.g., a drop in response rate), it signals a trend worth immediate investigation.
Why is this important?
Marking alerts as critical helps you:
Focus on high-impact issues:
- Not all anomalies are equally important. Critical alerts ensure you spend your time and resources addressing the most significant and recurring problems.
Reduce Alert Fatigue:
- By filtering out less significant anomalies, criticality ensures that your attention is directed toward meaningful deviations, minimizing distractions from false alarms or low-priority alerts.