The number of potential root causes has changed in cost anomaly detection!

[bwahn]

Previously, in almost all cases, only one potential root cause was shown, but now two or more are starting to appear. In this case, shouldn't the Athena table structure also be adjusted when configuring the data lake?

[iakov-aws]

Good point.

Indeed with this new feature we need to update the data structure. Right now only root cause #0 is shown.
https://github.com/awslabs/cid-framework/blob/main/data-collection/deploy/module-cost-anomaly.yaml#L209C1-L213C83

contributions are welcome. I would suggest to add an array of root causes as json in addition to the main root cause #0 for the backwards compatibility.