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 Monitor log profiles without retention poliy
Overview
Log profile retention in Azure can significantly impact cost management by controlling the amount of log data stored and the duration for which it is retained.
This pipeline allows you to specify a collection of log profiles without retention poliy 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
monitor_log_profiles_without_retention_policy_trigger_enabled
should be set totrue
as the default isfalse
.monitor_log_profiles_without_retention_policy_trigger_schedule
should be set to your desired running schedulemonitor_log_profiles_without_retention_policy_default_action
should be set to your desired action (i.e."notify"
for notifications or"enable_log_profile_retention"
to enable log profile retention).
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(lp.id, ' [', sub.subscription_id, ']') as title, lp.name, lp.subscription_id, lp.title, lp.sp_connection_name as connfrom azure_log_profile as lp left join azure_subscription as sub on lp.subscription_id = sub.subscription_idwhere lp.retention_policy ->> 'enabled' <> 'true';
Schedule
15m
Tags
category = Cost
class = unused
plugin = azure
service = Azure/Monitor