Allow an anomaly's status to be updated programmatically via the API.
The Anomalies API is currently read-only (GET /analytics/v1/anomalies and GET .../anomalies/{id}). There is no way to change the state of an anomaly through the API.
Please add a write path - for example PATCH /analytics/v1/anomalies/{id} -supporting an acknowledge / dismiss / resolve state transition, ideally with an optional note or external-reference field so an anomaly can be linked to a record in an external system. This would mirror the status-update capability the Insights API already provides via PATCH /insights/v1/sources/{sourceID}/insights/{insightKey}.
This may also merit adding another endpoint to the API for listing ackowledement reasons.
Use case:
Teams that automate FinOps workflows need to reflect an anomaly's resolution back in DoiT once it has been handled elsewhere. Without a write path, anomaly state can only be tracked outside DoiT, so the two views drift apart and the same anomaly gets reviewed repeatedly. A simple status write-back keeps DoiT aligned with downstream automation and avoids duplicate triage.
Dawid Piotrowski
shared this idea