4 results found
-
Supporting Threads functionality for DoiT Anomaly detection
Allow DoiT Anomaly detection users to create and manage threads for the the actions required to triage and resolve anomalies.
2 votes -
Ability to detect anomaly on monthly cost granularity
If there is a gradual increase in cost on daly basis such increase will not be considered as an anomaly as the data would look like an expected increase however if we compare this cost over month to month the increase can be significant. Hence it is worth generating anomalies on such cost spikes on Monthly granularity.
1 vote -
Enhance daily anomaly notification by adding granularity about the usage the timing when the spike actually happened
Add the context in the anomaly notification which is like highlighting the usage and cost impact along with the timing when it occurred during the day
An example: Hey, between 2-3AM on May 5th you had 150M requests which lead to a charge of 110$ and this is why we triggered the anomaly"
1 vote -
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.
1 vote
- Don't see your idea?