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 Compute disks with high IOPS
Overview
Compute disk with high IOPS cost money.
This query trigger detects Compute disks with high IOPS 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_with_high_iops_trigger_enabledshould be set totrueas the default isfalse.compute_disks_with_high_iops_trigger_scheduleshould be set to your desired running schedulecompute_disks_with_high_iops_default_actionshould be set to your desired action (i.e."notify"for notifications or"snapshot_and_delete_disk"to snapshot and delete the disk).
Then starting the server:
flowpipe serveror if you've set the variables in a .fpvars file:
flowpipe server --var-file=/path/to/your.fpvarsQuery
select concat( d.id, ' [', d.resource_group, '/', d.subscription_id, ']' ) as title, d.id as resource, d.name as disk_name, d.resource_group, d.subscription_id, d.name || to_char(current_date, 'YYYYMMDD') as snapshot_name, d.sp_connection_name as connfrom azure_compute_disk as d left join azure_subscription as sub on sub.subscription_id = d.subscription_idwhere d.disk_iops_read_write > var.compute_disk_max_iops_threshold;Schedule
15mTags
category = Cost
class = unused
plugin = azure
service = Azure/Compute