Autoscale allows you to adjust the amount of running resources to handle the load on your application.
- Add resources to handle increases in load and also save money by removing resources that are sitting idle.
- Specify a minimum and maximum number of instances to run and add or remove VMs automatically
based on a set of rules.
- Having a minimum makes sure your application is always running even under no load.
- Having a maximum limits your total possible hourly cost.
- Automatically scale between these two extremes using rules you create.
When rule conditions are met, one or more autoscale actions are triggered. You can add and remove VMs, or do other actions. The following conceptual diagram shows this process:
To set up the OpsRamp Azure integration and discover the Azure service,
go to Azure Integration Discovery Profile and select
|OpsRamp Metric||Metric Display Name||Unit||Aggregation Type||Description|
|azure_observed_metric_value||Observed Metric Value||Count||Average||Value computed by autoscale when executed.|
|azure_metric_threshold||Metric Threshold||Count||Average||The configured autoscale threshold when autoscale ran.|
|azure_observed_capacity||Observed Capacity||Count||Average||Capacity reported to autoscale when it executed.|
|azure_scale_actions_initiated||Scale Actions Initiated||Count||Total||Direction of the scale operation.|
- Configurable in OpsRamp Azure Integration Discovery Profile.