How Idle Resources Are Calculated

In addition to any native tools that might collect idle time data on your CSP, Optimize also collects and stores idle resource information in a database. The Optimize database provides idle time information if native tools, such as CloudTrail, are not enabled or not available.

Optimize can also provide approximations for idle times when complete data is not available for any resources. An example of this would be if a policy is set to report idle resources only after being idle for 10 days, but your Virtana Platform integration has only been active for 7 days.

vp-opt-drwg-idle-time.png

For Azure, we calculate idle period from our database. When a resource has been idle from the beginning of our observations, we assume that the full idle period is unknown. Otherwise, we calculate the exact idle period.

For AWS, we use CloudTrail to get the exact idle period. CloudTrail stores the data for the past 90 days. So, when the resource is idle for more than 90 days, the full idle period is unknown. The exact idle period can be determined when the resource is idle for less than 90 days

If CloudTrail is turned off for your account, we calculate idle period from our database. when a resource has been idle from the beginning of our observations, we assume that the full idle period is unknown. Otherwise, we calculate the exact idle period.