Health probes are essential for Azure Load Balancer to determine the health of backend instances and route traffic only to healthy ones. This section details the configuration and status of your configured health probes.
Configured Health Probes
Frontend HTTP Probe
Status: Healthy
(Monitoring 3 healthy instances)
Protocol
HTTP
Port
80
Interval (seconds)
5
Timeout (seconds)
2
Number of Retries
2
Path
/healthcheck.html
Description: This probe sends an HTTP GET request to the root path /healthcheck.html on port 80 of each backend instance every 5 seconds. If 2 consecutive probes fail (timeout after 2 seconds), the instance is considered unhealthy.
Probe History (Last 10 Checks)
| Timestamp |
Instance IP |
Status |
Details |
| 2023-10-27 10:30:15 |
10.0.0.4 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:30:10 |
10.0.0.5 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:30:05 |
10.0.0.6 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:30:00 |
10.0.0.4 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:29:55 |
10.0.0.5 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:29:50 |
10.0.0.6 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:29:45 |
10.0.0.4 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:29:40 |
10.0.0.5 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:29:35 |
10.0.0.6 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:29:30 |
10.0.0.4 |
Healthy |
Responded with 200 OK |
Internal TCP Probe (Port 8080)
Status: Healthy
(Monitoring 2 healthy instances)
Protocol
TCP
Port
8080
Interval (seconds)
10
Timeout (seconds)
3
Number of Retries
3
Description: This probe performs a TCP handshake on port 8080. It's used for backend services that don't expose an HTTP endpoint for health checks.
Probe History (Last 10 Checks)
| Timestamp |
Instance IP |
Status |
Details |
| 2023-10-27 10:30:20 |
10.0.0.7 |
Healthy |
TCP connection established |
| 2023-10-27 10:30:10 |
10.0.0.8 |
Healthy |
TCP connection established |
| 2023-10-27 10:30:00 |
10.0.0.7 |
Healthy |
TCP connection established |
| 2023-10-27 10:29:50 |
10.0.0.8 |
Healthy |
TCP connection established |
| 2023-10-27 10:29:40 |
10.0.0.7 |
Healthy |
TCP connection established |
| 2023-10-27 10:29:30 |
10.0.0.8 |
Healthy |
TCP connection established |
| 2023-10-27 10:29:20 |
10.0.0.7 |
Healthy |
TCP connection established |
| 2023-10-27 10:29:10 |
10.0.0.8 |
Healthy |
TCP connection established |
| 2023-10-27 10:29:00 |
10.0.0.7 |
Healthy |
TCP connection established |
| 2023-10-27 10:28:50 |
10.0.0.8 |
Healthy |
TCP connection established |
Sensitive API Probe (HTTPS)
Status: Degrading
(Monitoring 1 unhealthy instance)
Protocol
HTTPS
Port
443
Interval (seconds)
7
Timeout (seconds)
4
Number of Retries
1
Path
/api/v1/status
Description: This probe checks an HTTPS endpoint on port 443. It requires valid SSL certificates on the backend instances.
Probe History (Last 10 Checks)
| Timestamp |
Instance IP |
Status |
Details |
| 2023-10-27 10:30:18 |
10.0.0.9 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:30:11 |
10.0.0.10 |
Unhealthy |
SSL certificate verification failed |
| 2023-10-27 10:30:04 |
10.0.0.9 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:29:57 |
10.0.0.10 |
Unhealthy |
SSL certificate verification failed |
| 2023-10-27 10:29:50 |
10.0.0.9 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:29:43 |
10.0.0.10 |
Unhealthy |
SSL certificate verification failed |
| 2023-10-27 10:29:36 |
10.0.0.9 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:29:29 |
10.0.0.10 |
Unhealthy |
SSL certificate verification failed |
| 2023-10-27 10:29:22 |
10.0.0.9 |
Healthy |
Responded with 200 OK |
| 2023-10-27 10:29:15 |
10.0.0.10 |
Unhealthy |
SSL certificate verification failed |