1 result found
-
Re-alerting for an active anomaly if the cost spikes by 2X or 3X
Today, once we notify for an anomaly, we do not notify again if an anomaly is active but the cost has spiked by X times, lets say twice. As a result, customer who ignored the anomaly in first place based on its cost missed the opportunity to react when the cost spike became more considerable.
6 votesIn Development with a targeted release by Spring 8.3 (late Feb 2026)
- Don't see your idea?