On Azure, peak traffic shows up as Application Gateway 502s, SNAT port exhaustion on outbound calls and Redis client timeouts. The gateway's health probe and timeout decide which backends stay in the pool, so fix those first. Start with Fix Application Gateway 502 Bad Gateway at Peak.
- Fix Application Gateway 502 Bad Gateway at Peak
Give Application Gateway a cheap health probe and a request timeout sized from your p99, so busy backends stay in the pool and peak traffic stops getting 502.
- Fix StackExchange.Redis RedisTimeoutException on Azure
Read each Azure Cache for Redis timeout message, then fix the thread pool, the multiplexer or the server load it points to, so peak traffic stops timing out.
- Azure SNAT Port Exhaustion Alerts with Prometheus
Alert on failed SNAT connections and used ports per instance, so you catch App Service intermittent outbound connection errors before users report them.