We observed a steady increase in socket connections for your App Services from Monday evening (April 14) to Tuesday (April 15), but the request volume at the Application Gateway remained steady. Possible causes include longer open connections
, new code opening more connections
, App Service scaling
adding more instances, Azure managing connections to prevent source network address translation (SNAT
) exhaustion, or a connection
leak.
- Check recent
deployments
for any code changes made around Monday evening, even if they seem unrelated. - Make sure all connections and resources are properly
closed
, use connection pooling, and dispose of resources correctly. - Check
App Service logs
anddiagnostics
, enable diagnostics, look for exceptions inApplication Insights
, and review worker process restarts. -
Optimize connection management
by using persistent connections, connection pooling, retry policies with circuit breakers, and HTTP/2 to reduce overhead. - Check for
dependency issues by
reviewing changes in external services your app relies on and monitoring connection timeouts and response times.
Please refer to the document below for troubleshooting outbound connection errors in Azure App Service.
Please accept as "Yes" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.
Let me know if you have any further Queries.