Once someone uses cloud scanner to assess environmental impacts, the next question is often "Where to act".
Solution
This is mainly an idea list / very draft feature, to be discussed and designed further prior implementation
Cloud scanner (or maybe the visualization dashboard) could help the user by
highlighting resources that generate the most of impacts
identify underutilised resources like oversized vm's (this may imply to export additional metrics like CPU usage).
maybe also identify old data on buckets ?
Alternatives
Suggestions could also appear in CLI output.
But implementation may differ, mainly because when using metrics, we can use native prometheus / grafana functions to filter resources or average impacts of a criteria (metric) over a period of time.
Problem
Once someone uses cloud scanner to assess environmental impacts, the next question is often "Where to act".
Solution
This is mainly an idea list / very draft feature, to be discussed and designed further prior implementation
Cloud scanner (or maybe the visualization dashboard) could help the user by
Alternatives
Suggestions could also appear in CLI output. But implementation may differ, mainly because when using metrics, we can use native prometheus / grafana functions to filter resources or average impacts of a criteria (metric) over a period of time.
Additional context or elements