library
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 Compute disks unattached
Overview
Managing unattached disks is crucial for cost efficiency, as they continue to incur charges while not actively contributing to operational workloads. Regularly identifying and managing these resources can help optimize storage costs and organizational efficiency in Azure.
This query trigger detects unattached compute disks 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
compute_disks_if_unattached_trigger_enabled
should be set totrue
as the default isfalse
.compute_disks_if_unattached_trigger_schedule
should be set to your desired running schedulecompute_disks_if_unattached_default_action
should be set to your desired action (i.e."notify"
for notifications or"delete_disk"
to delete the disk).
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
Pipeline
Query
select concat( d.id, ' [', d.resource_group, '/', d.subscription_id, ']' ) as title, d.name, d.resource_group, d.subscription_id, d.name || to_char(current_date, 'YYYYMMDD') as snapshot_name, d._ctx ->> 'connection_name' as credfrom azure_compute_disk as d, azure_subscription as subwhere d.disk_state = 'Unattached' and sub.subscription_id = d.subscription_id;
Schedule
15m