Loading controls...
Control: Compute instances with low CPU utilization should be reviewed
Description
Resize or eliminate under utilized instances.
Usage
Run the control in your terminal:
steampipe check oci_thrifty.control.compute_instance_low_utilization
Snapshot and share results via Steampipe Cloud:
steampipe loginsteampipe check --share oci_thrifty.control.compute_instance_low_utilization
Plugins & Tables
Params
Args | Name | Default | Description | Variable |
---|---|---|---|---|
$1 | compute_instance_avg_cpu_utilization_low |
| The average CPU utilization required for instances to be considered infrequently used. This value should be lower than compute_instance_avg_cpu_utilization_high. | |
$2 | compute_instance_avg_cpu_utilization_high |
| The average CPU utilization required for instances to be considered frequently used. This value should be higher than compute_instance_avg_cpu_utilization_low. |
SQL
with core_instance_utilization as ( select id, round(cast(sum(maximum) / count(maximum) as numeric), 1) as avg_max, count(maximum) days from oci_core_instance_metric_cpu_utilization_daily where date_part('day', now() - timestamp) <= 30 group by id)select i.id as resource, case when avg_max is null then 'error' when avg_max < $1 then 'alarm' when avg_max < $2 then 'info' else 'ok' end as status, case when avg_max is null then 'Metrics not available for ' || i.title || '.' else i.title || ' averaging ' || avg_max || '% max utilization over the last ' || days || ' days.' end as reason, coalesce(c.name, 'root') as compartment, i.regionfrom oci_core_instance as i left join core_instance_utilization as u on u.id = i.id left join oci_identity_compartment as c on c.id = i.compartment_id;