Skip to content

Commit 3cdbedd

Browse files
committed
Re-removing the note about health checks and Premium
1 parent 119fb72 commit 3cdbedd

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

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

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -135,9 +135,6 @@ After providing your application's Health check path, you can monitor the health
135135
## Limitations
136136

137137
- Health check can be enabled for **Free** and **Shared** App Service Plans so you can have metrics on the site's health and setup alerts, but because **Free** and **Shared** sites can't scale out, any unhealthy instances won't be replaced. You should scale up to the **Basic** tier or higher so you can scale out to 2 or more instances and utilize the full benefit of Health check. This is recommended for production-facing applications as it will increase your app's availability and performance.
138-
- Health check should not be enabled on Premium Functions sites. Due to the rapid scaling of Premium Functions, the health check requests can cause unnecessary fluctuations in HTTP traffic. Premium Functions have their own internal health probes that are used to inform scaling decisions.
139-
140-
141138

142139
## Frequently Asked Questions
143140

0 commit comments

Comments
 (0)