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 SQL Databases exceeding max age
Overview
SQL Databases can be quite costly to retain, it is also likely that after a certain point in time they're no longer required and should be cleaned up to prevent further costs.
This pipeline allows you to specify a collection of SQL Databases and then either send notifications or attempt to perform a predefined corrective action upon the collection.
Getting Started
By default, this trigger is disabled, however it can be configured by setting the below variables
sql_database_exceeding_max_age_trigger_enabled
should be set totrue
as the default isfalse
.sql_database_exceeding_max_age_trigger_schedule
should be set to your desired running schedulesql_database_exceeding_max_age_default_action
should be set to your desired action (i.e."notify"
for notifications or"delete_sql_database"
to delete the SQL database).
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
select concat( db.id, ' [', db.resource_group, '/', db.subscription_id, ']' ) as title, db.name, db.resource_group, db.subscription_id, db.server_name as server_name, db.sp_connection_name as connfrom azure_sql_database as db, azure_subscription as subwhere date_part('day', now() - creation_date) > 90 and sub.subscription_id = db.subscription_id;
Schedule
15m
Tags
category = Cost
class = unused
plugin = azure
service = Azure/SQL