Skip to content

Commit f0c6381

Browse files
authored
Update load-balancer-manage-health-status.md
1 parent d03b3f7 commit f0c6381

File tree

1 file changed

+35
-37
lines changed

1 file changed

+35
-37
lines changed

articles/load-balancer/load-balancer-manage-health-status.md

Lines changed: 35 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -101,52 +101,48 @@ To retrieve the health status information via REST API, you need to do a two req
101101
102102
1. Use the following POST request to obtain the Location URI from the Response Headers.
103103

104-
```rest
105-
106-
107-
POST https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/loadBalancers/<loadBalancerName>/loadBalancingRules/<loadBalancingRulesName>/health?api-version=2024-03-01&preserve-view=true
108-
Authorization: Bearer <access token>
109-
110-
```
104+
```rest
105+
POST https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/loadBalancers/<loadBalancerName>/loadBalancingRules/<loadBalancingRulesName>/health?api-version=2024-03-01&preserve-view=true
106+
Authorization: Bearer <access token>
107+
```
111108
112109
1. Copy the Location URI from the Response Headers. Location URI should follow this schema.
113110
114-
```rest
115-
https://management.azure.com/subscriptions/<subscriptionId>/providers/Microsoft.Network/locations/<locationName>/operationResults/<operationResultsId>?api-version=2024-03-01&preserve-view=true
116-
```
111+
```rest
112+
https://management.azure.com/subscriptions/<subscriptionId>/providers/Microsoft.Network/locations/<locationName>/operationResults/<operationResultsId>?api-version=2024-03-01&preserve-view=true
113+
```
117114

118115
1. Use the copied Location URI to make a GET request.
119116

120-
```rest
121-
GET https://management.azure.com/subscriptions/<subscriptionId>/providers/Microsoft.Network/locations/<locationName>/operationResults/<operationResultsId>?api-version=2024-03-01&preserve-view=true
122-
123-
Authorization: Bearer <access token>
124-
125-
```
117+
```rest
118+
GET https://management.azure.com/subscriptions/<subscriptionId>/providers/Microsoft.Network/locations/<locationName>/operationResults/<operationResultsId>?api-version=2024-03-01&preserve-view=true
119+
120+
Authorization: Bearer <access token>
121+
```
126122

127123
1. A status code of 200 is returned and the health status information is displayed in the response body similar to this example response:
128124

129-
```JSON
130-
{
131-
"up": 2,
132-
"down": 0,
133-
"loadBalancerBackendAddresses": [
134-
{
135-
"ipAddress": "10.0.2.5",
136-
"networkInterfaceIPConfigurationId": "/subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/networkInterfaces/<networkInterfaceName>/ipConfigurations/<ipConfigurationName>",
137-
"state": "Up",
138-
"reason": "Up_Admin"
139-
},
140-
{
141-
"ipAddress": "10.0.2.4",
142-
"networkInterfaceIPConfigurationId": "/subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/networkInterfaces/<networkInterfaceName>/ipConfigurations/<ipConfigurationName>",
143-
"state": "Up",
144-
"reason": "Up_Probe_Success"
145-
}
146-
]
147-
}
148-
149-
```
125+
```JSON
126+
{
127+
"up": 2,
128+
"down": 0,
129+
"loadBalancerBackendAddresses": [
130+
{
131+
"ipAddress": "10.0.2.5",
132+
"networkInterfaceIPConfigurationId": "/subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/networkInterfaces/<networkInterfaceName>/ipConfigurations/<ipConfigurationName>",
133+
"state": "Up",
134+
"reason": "Up_Admin"
135+
},
136+
{
137+
"ipAddress": "10.0.2.4",
138+
"networkInterfaceIPConfigurationId": "/subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/networkInterfaces/<networkInterfaceName>/ipConfigurations/<ipConfigurationName>",
139+
"state": "Up",
140+
"reason": "Up_Probe_Success"
141+
}
142+
]
143+
}
144+
145+
```
150146

151147
## Design considerations
152148

@@ -164,3 +160,5 @@ When using the health status feature, consider the following limitations:
164160
- Health status isn’t supported for Gateway Load Balancer.
165161

166162
## Next steps
163+
> [!div class="nextstepaction"]
164+
> [Create a public load balancer with an IP-based backend using the Azure portal](tutorial-load-balancer-ip-backend-portal)

0 commit comments

Comments
 (0)