Skip to content

Commit 02c0b51

Browse files
added json
1 parent 4e54fe0 commit 02c0b51

File tree

1 file changed

+43
-1
lines changed

1 file changed

+43
-1
lines changed

articles/load-balancer/load-balancer-custom-probe-overview.md

Lines changed: 43 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,19 @@ A TCP probe fails when:
6565
* The TCP listener on the instance doesn't respond at all during the timeout period. A probe is marked down based on the number of failed probe requests, which were configured to go unanswered before marking the probe down.
6666
* The probe receives a TCP reset from the instance.
6767

68+
#### ARM template
69+
70+
```json
71+
{
72+
"name": "tcp",
73+
"properties": {
74+
"protocol": "Tcp",
75+
"port": 1234,
76+
"intervalInSeconds": 5,
77+
"numberOfProbes": 2
78+
},
79+
```
80+
6881
### <a name="httpprobe"></a> <a name="httpsprobe"></a> HTTP / HTTPS probe
6982

7083
> [!NOTE]
@@ -81,6 +94,36 @@ An HTTP / HTTPS probe fails when:
8194
* Probe endpoint doesn't respond at all during the a 31 second timeout period. Depending on the timeout value that is set, multiple probe requests might go unanswered before the probe gets marked as not running (that is, before SuccessFailCount probes are sent).
8295
* Probe endpoint closes the connection via a TCP reset.
8396

97+
#### ARM templates
98+
99+
- HTTP probe
100+
101+
```json
102+
{
103+
"name": "http",
104+
"properties": {
105+
"protocol": "Http",
106+
"port": 80,
107+
"requestPath": "/",
108+
"intervalInSeconds": 5,
109+
"numberOfProbes": 2
110+
},
111+
```
112+
113+
- HTTPS probe
114+
115+
```json
116+
{
117+
"name": "https",
118+
"properties": {
119+
"protocol": "Https",
120+
"port": 443,
121+
"requestPath": "/",
122+
"intervalInSeconds": 5,
123+
"numberOfProbes": 2
124+
},
125+
```
126+
84127
### <a name="guestagent"></a>Guest agent probe (Classic only)
85128

86129
Cloud service roles (worker roles and web roles) use a guest agent for probe monitoring by default. You should consider this an option of last resort. You should always define an health probe explicitly with a TCP or HTTP probe. A guest agent probe is not as effective as explicitly defined probes for most application scenarios.
@@ -166,4 +209,3 @@ Basic public Load Balancer exposes health probe status summarized per backend po
166209
- [Get started creating a public load balancer in Resource Manager by using PowerShell](load-balancer-get-started-internet-arm-ps.md)
167210
- [REST API for health probes](https://docs.microsoft.com/rest/api/load-balancer/loadbalancerprobes/)
168211
- Request new health probe abilities with [Load Balancer's Uservoice](https://aka.ms/lbuservoice)
169-

0 commit comments

Comments
 (0)