Hi @AnuragSingh-MSFT
There is no right or wrong way to configure monitoring; it depends on each application.
What is recommended is to scale up quickly (two instances at a time) and scale down slowly, shutting down one instance at a time.
If the application consumes a lot of memory, a good metric is to set an alert at 70% memory usage and start scaling up the VMs at 75% memory usage.
To configure you can go
- In the VMSS pane, select "Alerts" under the "Monitoring" section.
- Click on "New alert rule".
- In the "Create alert rule" page, the scope is automatically set to the VMSS you've selected. The scope defines the target resource(s) for the alert.
- Click on "Add condition".
- In the "Select a signal" pane, choose the metric or log signal you want to base your alert on (e.g., CPU usage, Memory usage, Disk I/O, etc.).
- Click on "Add action group" to define what happens when an alert is triggered.
- Configure the action group by providing a name, short name, and selecting the necessary actions (e.g., email, SMS, webhook, etc.).
Get in touch if you need more help with this issue.
--please don't forget to "[Accept the answer]" if the reply is helpful--