Skip to content

Commit 5794ceb

Browse files
author
Jason Freeberg
authored
Update monitor-instances-health-check.md
1 parent 6fc2103 commit 5794ceb

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/app-service/monitor-instances-health-check.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,8 @@ This article uses Health check in the Azure portal to monitor App Service instan
2525
- Furthermore, when scaling up or out, App Service pings the Health check path to ensure new instances are ready.
2626

2727
> [!NOTE]
28-
>- Health check doesn't follow 302 redirects. At most one instance will be replaced per hour, with a maximum of three instances per day per App Service Plan.
28+
>- Health check doesn't follow 302 redirects.
29+
>- At most one instance will be replaced per hour, with a maximum of three instances per day per App Service Plan.
2930
>- Note, if your health check is giving the status `Waiting for health check response` then the check is likely failing due to an HTTP status code of 307, which can happen if you have HTTPS redirect enabled but have `HTTPS Only` disabled.
3031
3132
## Enable Health Check

0 commit comments

Comments
 (0)