Skip to content

Commit 656c1e6

Browse files
committed
adding swap guidance
1 parent 5187357 commit 656c1e6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -203,7 +203,7 @@ Imagine you have two applications (or one app with a slot) with Health check ena
203203
If all instances of your application are unhealthy, App Service won't remove instances from the load balancer. In this scenario, taking all unhealthy app instances out of the load balancer rotation would effectively cause an outage for your application. However, the instance replacement will still occur.
204204

205205
### What happens during a slot swap?
206-
Health check configuration is not slot-specific, so after a swap, the Health check configuration of the swapped slot will be applied to the destination slot and vice-versa. For example, if you have Health Check enabled for your staging slot the endpoint configured will be applied to the production slot after a swap.
206+
Health check configuration is not slot-specific, so after a swap, the Health check configuration of the swapped slot will be applied to the destination slot and vice-versa. For example, if you have Health Check enabled for your staging slot the endpoint configured will be applied to the production slot after a swap. We recommend using consistent configuration for both production and non-production slots if possible to prevent any unexpected behavior after the swap.
207207

208208
### Does Health check work on App Service Environments?
209209

0 commit comments

Comments
 (0)