Skip to content

Commit e007c35

Browse files
authored
Clarify autoscaling availability metrics note
As suggested by @jaesoni, updated note on autoscaling behavior to clarify expected dips in availability metrics during scaling transitions.
1 parent 9895694 commit e007c35

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/application-gateway/application-gateway-autoscaling-zone-redundant.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ However, it’s important to note that provisioning a new instance may take appr
3636
For scale-in events, Application Gateway drains existing connections for 5 minutes on the instance that is subject for removal. After 5 minutes, existing connections are closed and the instance removed. Any new connections during or after the 5 minute scale-in time is established to other existing instances on the same gateway.
3737

3838
> [!NOTE]
39-
> During periods of frequent autoscaling activity (rapid upscale and downscale events in quick succession), you may observe temporary dips in the Public IP availability metric. This behavior is expected as Azure infrastructure probes the Application Gateway's Virtual Machine Scale Set during scaling transitions. These dips are typically brief and don't indicate a service issue. For environments with unstable traffic patterns that trigger frequent scaling events, consider adjusting your minimum instance count to reduce scaling frequency.
39+
> During autoscaling events, brief dips in availability metrics may be observed. This behavior is expected during scaling transitions and typically resolves within seconds.
4040
4141
## Next steps
4242

0 commit comments

Comments
 (0)