Recommendations based on Anomaly Acknowledgement
DCI should be able to provide recommendations based on Anomaly status in the Anomaly acknowledgement flow.
One such use case is customer acknowledge an anomaly with: "No, this wasn't an anomaly" . System can check notification settings to see if this customer has configuration to suppress the anomalies based on severity or cost threshold. If not, we can make such recommendations to the customer or send notifications so that they can avoid such noise in the future.
AdminGaurav Juneja
(Senior Product Manager, DoiT)
shared this idea
-
Nikola Keskinov commented
One addition that could even potentially simplify the implementation. Instead of trying to implicitly deduct if the customer found the anomaly too low for the threshold they have in mind for what an anomaly means, we could also add an option in the anomaly acknowledgment that says something along "The spike is too low to be considered an anomaly". This would be the exact use case for applying anomaly thresholds.