You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-instance-repairs.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,33 +159,33 @@ After updating the model of an existing scale set, ensure that the latest model
159
159
160
160
You can modify the automatic repairs policy of an existing scale set through the Azure portal.
161
161
162
-
> **NOTE**
163
-
> Make sure you have [Application Health extension](./virtual-machine-scale-sets-health-extension.md) or [Load balancer health probes](../load-balancer/load-balancer-custom-probe-overview.md)enabled on your VMSS before following the below steps.
162
+
> [!NOTE]
163
+
> Enable the [Application Health extension](./virtual-machine-scale-sets-health-extension.md) or [Load Balancer health probes](../load-balancer/load-balancer-custom-probe-overview.md) on your Virtual Machine Scale Sets before you start the next steps.
164
164
165
165
1. Go to an existing Virtual Machine Scale Set.
166
166
2. Under **Settings** in the menu on the left, select **Health and repair**.
167
167
3. Enable the **Monitor application health** option.
168
168
169
-
If you are monitoring your scale set using Application Health extension:
169
+
If you're monitoring your scale set by using the Application Health extension:
170
170
171
-
4. Choose **Application Health extension** from the Application health monitor dropdown list.
172
-
5. From **Protocol** dropdown list, choose the network protocol used by your application to report health. Select the appropriate protocol based on your application requirements. Protocol options are **HTTP, HTTPS** or **TCP**.
171
+
4. Choose **Application Health extension** from the Application Health monitor dropdown list.
172
+
5. From the **Protocol** dropdown list, choose the network protocol used by your application to report health. Select the appropriate protocol based on your application requirements. Protocol options are **HTTP, HTTPS**, or **TCP**.
173
173
6. In the **Port number** configuration box, type the network port used to monitor application health.
174
-
7. For **Path**, provide the application endpoint path (e.g. "/") used to report application health.
174
+
7. For **Path**, provide the application endpoint path (for example, "/") used to report application health.
175
175
176
-
> **NOTE**
177
-
> Application Health extension will ping this path inside each virtual machine in the scale set to get application health status for each instance. If you are using [Binary Health States](./virtual-machine-scale-sets-health-extension.md#binary-health-states) and the endpoint responds with a status 200 (OK), then the instance is marked as "Healthy". In all the other cases (including if the endpoint is unreachable), the instance is marked "Unhealthy". For more health state options, explore [Rich Health States](./virtual-machine-scale-sets-health-extension.md#binary-versus-rich-health-states).
176
+
> [!NOTE]
177
+
> The Application Health extension will ping this path inside each virtual machine in the scale set to get application health status for each instance. If you're using [Binary Health States](./virtual-machine-scale-sets-health-extension.md#binary-health-states) and the endpoint responds with a status 200 (OK), then the instance is marked as "Healthy". In all the other cases (including if the endpoint is unreachable), the instance is marked "Unhealthy". For more health state options, explore [Rich Health States](./virtual-machine-scale-sets-health-extension.md#binary-versus-rich-health-states).
178
178
179
-
If you are monitoring your scale set using SLB Health probes:
179
+
If you're monitoring your scale set using SLB Health probes:
180
180
181
-
8. Choose **Load balancer probe** from the Application health monitor dropdown list
182
-
9. For Load balancer health probe, select an existing health probe or create a new health probe for monitoring
181
+
8. Choose **Load balancer probe** from the Application Health monitor dropdown list.
182
+
9. For the Load Balancer health probe, select an existing health probe or create a new health probe for monitoring.
183
183
184
184
To enable automatic repairs:
185
185
186
186
10. Locate the **Automatic repair policy** section. Automatic repairs can be used to delete unhealthy instances from the scale set and create new ones to replace them.
187
187
11. Turn **On** the **Automatic repairs** option.
188
-
12. In **Grace period (min)**, specify the grace period in minutes, allowed values are between 10 and 90 minutes.
188
+
12. In **Grace period (min)**, specify the grace period in minutes. Allowed values are between 10 and 90 minutes.
0 commit comments