Add acknowledgement and alert dates to Cost Anomalies API
Would it be possible to add new fields to the data returned by Anomalies API? Namely:
- acknowledgement timestamp
- first notification sent timestamp (as this is not the same as anomaly start)
These pieces of data are critical for tracking internal SLAs on cost anomalies but are currently missing and have to be inferred and approximated from other sources.
Dawid Piotrowski
shared this idea
Thanks for submitting this idea!
This is a quick confirmation that we will review this in the near future.
Preliminary comments:
- The Acknowledgment timestamp sounds like a straightforward improvement.
- The timestamp of the first notification sent could get more nuanced, as a single anomaly could be sent to multiple channels, so we will aim for a solution that would be both feasible to implement and valuable for customers.
-
Dawid Piotrowski
commented
Thanks for the follow-up. I hope this can get implemented in foreseeable future.
As for the notification timestamp, I get your point. Perhaps this could be implemented as an array of "notification" objects, each with details like timestamp, channel and possibly some other fields. That may be useful for tracking, especially now with re-notifications enabled.