Skip to main content
Azure Data Explorer clusters are billed for their compute instances, whose SKU and count you choose. Azure Advisor compares a cluster’s use with what other SKUs offer and recommends a more cost-effective one. nOps imports these recommendations, checks them against your bill, and shows the estimated monthly saving with the current and target SKU.

Why it matters

Clusters are often created on a large SKU for a first load and never resized, and compute is most of their cost.

How nOps finds it

This recommendation comes from Azure Advisor, which looks at the cluster’s CPU, cache and ingestion use and recommends a target SKU. nOps imports Advisor’s recommendations daily and checks each one against your own Azure bill for the last 7 complete days: the resource must still be billed in the last 3 days of that window, and Advisor’s estimate is capped at what the resource actually cost (Advisor prices at pay-as-you-go rates, so you may pay less through discounts, reservations or savings plans). Recommendations worth less than $1 a month are left out.

Before you start

Permission to scale the cluster, and a check that the target SKU’s cache size fits your hot data.

How to implement

  1. Review the recommended SKU and confirm its cache (SSD) size still holds the data your queries need hot.
  2. In the Azure portal, open the cluster and go to Scale up. Choose the recommended SKU and apply.
  3. Or use the Azure CLI: az kusto cluster update --resource-group RESOURCE_GROUP --name CLUSTER --sku name=SKU tier=Standard.
  4. Update Terraform, Bicep or ARM templates so a later deployment does not change it back.

Risks and considerations

  • Changing SKU moves the cluster to new instances and can take a while; plan it outside busy hours.
  • A smaller cache can make queries on older data slower.
  • To roll back, scale back up to the original SKU.