Detect & correct Kusto clusters without autoscaling

Enabling autoscaling for Azure Kusto clusters can significantly optimize costs, especially in environments with fluctuating workloads. Autoscaling adjusts the number of resources based on demand, ensuring you are not over-provisioning and paying for unused capacity.

Getting Started

By default, this trigger is disabled, however it can be configured by setting the below variables

kusto_clusters_without_autoscaling_trigger_enabled should be set to true as the default is false.
kusto_clusters_without_autoscaling_trigger_schedule should be set to your desired running schedule
kusto_clusters_without_autoscaling_default_action should be set to your desired action (i.e. "notify" for notifications or "stop_kusto_cluster" to stop the kusto cluster).

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

Correct Kusto clusters without autoscaling

Query

select
  concat(
    kc.id,
    ' [',
    kc.resource_group,
    '/',
    kc.subscription_id,
    ']'
  ) as title,
  kc.id as id,
  kc.name,
  kc.resource_group,
  kc.subscription_id,
  kc.sp_connection_name as conn
from
  azure_kusto_cluster as kc,
  azure_subscription as sub
where
  sub.subscription_id = kc.subscription_id
  and optimized_autoscale is null;

Schedule

15m

Detect & correct Kusto clusters without autoscaling

Getting Started

Pipeline

Query

Schedule

Tags