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-health-extension.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -170,8 +170,8 @@ The following JSON shows the schema for the Rich Health States extension. The ex
170
170
| protocol |`http` or `https` or `tcp`| string |
171
171
| port | Optional when protocol is `http` or `https`, mandatory when protocol is `tcp`| int |
172
172
| requestPath | Mandatory when protocol is `http` or `https`, not allowed when protocol is `tcp`| string |
173
-
| intervalInSeconds | Optional, default is 5 seconds. This is the interval between each health probe. For example, if intervalInSeconds == 5, a probe will be sent to the local application endpoint once every 5 seconds. | int |
174
-
| numberOfProbes | Optional, default is 1. This is the number of consecutive probes required for the health status to change. For example, if numberOfProbles == 3, you will need 3 consecutive "Healthy" signals to change the health status from "Unhealthy"/"Unknown" into "Healthy" state. The same requirement applies to change health status into "Unhealthy" or "Unknown" state. | int |
173
+
| intervalInSeconds | Optional, default is 5 seconds. This is the interval between each health probe. For example, if intervalInSeconds == 5, a probe will be sent to the local application endpoint once every 5 seconds. Minimum value is 5 seconds, maximum is 60 seconds. | int |
174
+
| numberOfProbes | Optional, default is 1. This is the number of consecutive probes required for the health status to change. For example, if numberOfProbles == 3, you will need 3 consecutive "Healthy" signals to change the health status from "Unhealthy"/"Unknown" into "Healthy" state. The same requirement applies to change health status into "Unhealthy" or "Unknown" state. Minimum value is 1 probe, maximum is 3 probes. | int |
175
175
| gracePeriod | Optional, default = `intervalInSeconds` * `numberOfProbes`; maximum grace period is 7200 seconds | int |
176
176
177
177
## Binary Health States
@@ -243,8 +243,8 @@ The following JSON shows the schema for the Application Health extension. The ex
243
243
| protocol |`http` or `https` or `tcp`| string |
244
244
| port | Optional when protocol is `http` or `https`, mandatory when protocol is `tcp`| int |
245
245
| requestPath | Mandatory when protocol is `http` or `https`, not allowed when protocol is `tcp`| string |
246
-
| intervalInSeconds | Optional, default is 5 seconds. This is the interval between each health probe. For example, if intervalInSeconds == 5, a probe will be sent to the local application endpoint once every 5 seconds. | int |
247
-
| numberOfProbes | Optional, default is 1. This is the number of consecutive probes required for the health status to change. For example, if numberOfProbles == 3, you will need 3 consecutive "Healthy" signals to change the health status from "Unhealthy" into "Healthy" state. The same requirement applies to change health status into "Unhealthy" state. | int |
246
+
| intervalInSeconds | Optional, default is 5 seconds. This is the interval between each health probe. For example, if intervalInSeconds == 5, a probe will be sent to the local application endpoint once every 5 seconds. Minimum value is 5 seconds, maximum is 60 seconds. | int |
247
+
| numberOfProbes | Optional, default is 1. This is the number of consecutive probes required for the health status to change. For example, if numberOfProbles == 3, you will need 3 consecutive "Healthy" signals to change the health status from "Unhealthy" into "Healthy" state. The same requirement applies to change health status into "Unhealthy" state. Minimum value is 1 probe, maximum is 3 probes.| int |
248
248
249
249
## Deploy the Application Health extension
250
250
There are multiple ways of deploying the Application Health extension to your scale sets as detailed in the following examples.
Copy file name to clipboardExpand all lines: articles/virtual-machines/extensions/health-extension.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -174,8 +174,8 @@ The following JSON shows the schema for the Application Health extension. The ex
174
174
| protocol |`http` or `https` or `tcp`| string |
175
175
| port | Optional when protocol is `http` or `https`, mandatory when protocol is `tcp`| int |
176
176
| requestPath | Mandatory when protocol is `http` or `https`, not allowed when protocol is `tcp`| string |
177
-
| intervalInSeconds | Optional, default is 5 seconds. This setting is the interval between each health probe. For example, if intervalInSeconds == 5, a probe is sent to the local application endpoint once every 5 seconds. | int |
178
-
| numberOfProbes | Optional, default is 1. This setting is the number of consecutive probes required for the health status to change. For example, if numberOfProbles == 3, you will need 3 consecutive "Healthy" signals to change the health status from "Unhealthy" into "Healthy" state. The same requirement applies to change health status into "Unhealthy" state. | int |
177
+
| intervalInSeconds | Optional, default is 5 seconds. This setting is the interval between each health probe. For example, if intervalInSeconds == 5, a probe is sent to the local application endpoint once every 5 seconds. Minimum value is 5 seconds, maximum is 60 seconds. | int |
178
+
| numberOfProbes | Optional, default is 1. This setting is the number of consecutive probes required for the health status to change. For example, if numberOfProbles == 3, you will need 3 consecutive "Healthy" signals to change the health status from "Unhealthy" into "Healthy" state. The same requirement applies to change health status into "Unhealthy" state. Minimum value is 1 probe, maximum is 3 probes.| int |
179
179
180
180
## Extension schema for Rich Health States
181
181
@@ -223,8 +223,8 @@ The following JSON shows the schema for the Rich Health States extension. The ex
223
223
| protocol |`http` or `https` or `tcp`| string |
224
224
| port | Optional when protocol is `http` or `https`, mandatory when protocol is `tcp`| int |
225
225
| requestPath | Mandatory when protocol is `http` or `https`, not allowed when protocol is `tcp`| string |
226
-
| intervalInSeconds | Optional, default is 5 seconds. This setting is the interval between each health probe. For example, if intervalInSeconds == 5, a probe is sent to the local application endpoint once every 5 seconds. | int |
227
-
| numberOfProbes | Optional, default is 1. This setting is the number of consecutive probes required for the health status to change. For example, if numberOfProbles == 3, you will need 3 consecutive "Healthy" signals to change the health status from "Unhealthy"/"Unknown" into "Healthy" state. The same requirement applies to change health status into "Unhealthy" or "Unknown" state. | int |
226
+
| intervalInSeconds | Optional, default is 5 seconds. This setting is the interval between each health probe. For example, if intervalInSeconds == 5, a probe is sent to the local application endpoint once every 5 seconds. Minimum value is 5 seconds, maximum is 60 seconds. | int |
227
+
| numberOfProbes | Optional, default is 1. This setting is the number of consecutive probes required for the health status to change. For example, if numberOfProbles == 3, you will need 3 consecutive "Healthy" signals to change the health status from "Unhealthy"/"Unknown" into "Healthy" state. The same requirement applies to change health status into "Unhealthy" or "Unknown" state. Minimum value is 1 probe, maximum is 3 probes.| int |
228
228
| gracePeriod | Optional, default = `intervalInSeconds` * `numberOfProbes`; maximum grace period is 7200 seconds | int |
0 commit comments