See the number of outbound tcp connections (OpenSocketCount) and the count for each web app within a particular app service plan.
See the number of outbound tcp connections (OpenSocketCount) for each web app within a particular app service plan. I have had issues were all web apps in that service plan were failing when accessing sql server or service bus relay (anything that needs an outgoing tcp connection) because the number of open tcp connections exceeded the plan limit. I had to request the information from support to figure out what web apps had the majority of the open sockets.
The only option that I have found is this...
Which is not available in any of the plethora of Azure metric tools.
We need to be able to query these metrics in log analytics and be able to set alerts.
I recently experienced issues that turned out to be SNAT related due to open TCP connections. The support agent who discovered that SNAT issues were the underlying cause of various mysterious timeouts and exceptions arising from no more TCP connections available told us that Microsoft's "Best Practice" was to have no more than 100 concurrent TCP connections open. When I asked where in the Azure portal metrics I could see total # of concurrent TCP connections over time, they told me there is no way to see that in the Azure portal, and that only support staff could see that...leaving us to constantly check in with the Agent to gauge how effective our refactoring efforts were.
If Microsoft is suggesting a "Best Practice" regarding concurrent TCP connections, then Microsoft should provide a way for us to actually see metrics relating to that.