standard
turbot/azure_thrifty
- Detect & correct App Service plans if unused
- Detect & correct Compute disks attached to stopped VMs
- Detect & correct Compute unattached disks
- Detect & correct Compute disks with high IOPS
- Detect & correct Compute disks with low usage
- Detect & correct Compute snapshots exceeding max age
- Detect & correct Compute snapshots with premium storage
- Detect & correct Compute virtual machines
- Detect & correct Compute virtual machine with low utilization
- Detect & correct Compute disks exceeding max size
- Detect & correct HDInsight clusters exceeding max age
- Detect & correct Kubernetes clusters exceeding max age
- Detect & correct Kusto clusters exceeding max age
- Detect & correct Kusto clusters without autoscaling
- Detect & correct Monitor log profiles without retention policy
- Detect & correct Network application gateways without autoscaling
- Detect & correct Network load balancers if unused
- Detect & correct Network NAT gateways if unused
- Detect & correct Network unattached public IPs
- Detect & correct Network virtual network gateways if unused
- Detect & correct Service Fabric clusters exceeding max age
- Detect & correct SQL databases exceeding max age
- Detect & correct Storage accounts without lifecycle policy
- Detect & correct Compute virtual machine scale sets if unused
Get Involved
Version
Detect & correct Virtual Machine Scale Sets if unused
Overview
Virtual Machine Scale Sets with no instances attached still cost money and should be deleted.
This pipeline detects unused Virtual Machine Scale Sets and then either sends a notification or attempts to perform a predefined corrective action.
Getting Started
By default, this trigger is disabled, however it can be configured by setting the below variables
virtual_machine_scale_sets_if_unused_trigger_enabled
should be set totrue
as the default isfalse
.virtual_machine_scale_sets_if_unused_trigger_schedule
should be set to your desired running schedulevirtual_machine_scale_sets_if_unused_default_action
should be set to your desired action (i.e."notify"
for notifications or"delete_virtual_machine_scale_set"
to delete the virtual machine scale set).
Then starting the server:
flowpipe server
or if you've set the variables in a .fpvars
file:
flowpipe server --var-file=/path/to/your.fpvars
Query
with scale_set_vm_count as ( select count(*), scale_set_name, resource_group, region, subscription_id from azure_compute_virtual_machine_scale_set_vm group by scale_set_name, resource_group, region, subscription_id)select concat( vmss.id, ' [', vmss.resource_group, '/', vmss.subscription_id, ']' ) as title, vmss.id as id, vmss.name, vmss.resource_group, vmss.subscription_id, vmss.sp_connection_name as connfrom azure_compute_virtual_machine_scale_set as vmss left join scale_set_vm_count as vm on vm.scale_set_name = vmss.name and vm.resource_group = vmss.resource_group and vm.region = vmss.region left join azure_subscription as sub on sub.subscription_id = vmss.subscription_idwhere vm.scale_set_name is null;
Schedule
15m
Tags
category = Cost
class = unused
plugin = azure
service = Azure/Compute