Is it possible to add dynamic number of instances in an Azure Virtual Machine Scaleset autoscale rule? As shown in the image, can I pass a variable for the instance count for scaling out?
I'm afraid you cannot do it. When you do it, it will show the limitations:
Just imagine, we can't know when it will scale the instances so that we cannot know what is the time to set the variable with an exact number. So it must be a valid number without empty. And the number between 1 and 512 is a limitation set by Azure.
Related
My Azure SQL Managed Instance is showing the storage utilization chart as follows:
And the Average Storage used metric is showing as follows:
Goal: set a condition for the metric Storage Space used so that when the average space used exceeds 52k, I get an alert. Currently, average storage used is showing 51.74k as depicted in the image 2 below)
Question: what threshold value should I set in the Alert Rule, to achieve the above goal?
Ref: Create alerts for Azure SQL Managed Instance
Please configure in the Alert panel as shown below for a threshold limit of 52k.
Select Unit as "k" and Threshold value as 52
Azure Portal provides the ability to set the number of instances an app can scale out to. This is set by the Maximum Burst option in the Scale out tab:
Picture link since I can't post pictures yet
The maximum number of instances can be further be limited by the Maximum Scale Out Limit.
So, the question is, why and when should I put different values in those and what is the actual difference between those settings?
They all represent the maximum number of instances, but Maximum Burst represents the maximum number of instances that the plan can scale out, and Maximum Scale Out Limit represents the maximum number of instances that the current Function App can scale out.
If you set the maximum number of instances of the plan, then the maximum number of instances of your Function App cannot exceed the maximum number of instances of the plan.
I have changed the size of the Scale Set to Standard D8 from Standard D1, even after few hours my ScaleSet instance size is just D1. How can I change this newly updated size to ScaleSet Instances?
In the screenshot you shared, it says "LATEST MODEL: No". This implies:
Your upgradePolicy setting is set to Manual.
You updated the scale set model (with the new VM size), but did not apply the update to the VMs in the scale set, which you need to do if the upgradePolicy is set to Manual. You can apply these updates in the Instances tab for a Scale Set in the Azure portal for example.
You can find out more about the upgradePolicy setting here: https://msftstack.wordpress.com/2016/11/15/azure-scale-set-upgrade-policy-explained/
In the new Azure portal under
Cloud services > Scaling blade > Scale Profile > choosing Recurrence
There is a range of instances to choose, if I understood correctly.
Can someone explain the meaning of a "range", since in certain hour I would expect to have a fixed number of instances.
New portal
The range defines the minimum and maximum number of instances that will be running at any given time. For example, if you're configuring a scale profile based on CPU load you will have CPU percentage rules in place that will add/remove instances based on CPU thresholds you define. The scale profile will add/remove instances as needed within the range you specified.
The Range in the new Portal has 2 sliders Minimum and Max Number of Instances
Depending on the trigger you will set for this to Happen
Manual Scale : The Nummber of Instances will be set based on your Choice
CPU : You set the Minimum and the Max for Instances and Besed on the CPU Untalization Azure will Set the Number of instances
Other Measures : Same as CPU but for Queuing, Traffic, Disk I/O Etc.
There is "Scale Profile" and also a sub scaling call "rule".
The rule determine the scale within the range of the "Scale Profile".
target range for the metric. For example, if you chose CPU percentage, you can set a target for the average CPU across all of the instances in your service. A scale out will happen when the average CPU exceeds the maximum you define, likewise, a scale in will happen whenever the average CPU drops below the minimum
https://learn.microsoft.com/en-us/azure/monitoring-and-diagnostics/insights-how-to-scale
This picture should show it all:
As you can see the minimum instance is set on three, but autoscale decides to first scale up, and than scale back down again - below the minimum.
I guess even if the CPU is far below the target I assume it should never go below the minimum. Why is this happening? Do I need to set somewhere else a setting?
Oops. Apparently I had set up a day / night time schedule, and at this certain point it went to the night time schedule where it was min/max 1 instance.