When adding new instances to the LoadBalancer, scale out mechanism doesn't wait for those application instances to fully warm up.
Availability checker, via AppInsights, logs these responses, with the header:
Which means that IIS knows that the application is in it's WarmUp cycle, but the LoadBalancer is already trying to serve requests.
N.B. we _can_ add a rewrite rule to redirect the user to the original request, and hope that the LoadBalancer sends the user to a ready instance - but this feels like a hack.242 votes
Thanks for the feedback. We are thinking of ways to make the warmup model better and fully ready for the app’s traffic. Right now, we just see the instance is ready before directing traffic.
Please refer to this blog post for more information about slots and AppInit.
When you deploy an App Service into an App Service Environment behind an ILB, much of the UI is greyed out. Examples of this is the 'Connect' button, 'Log Stream', 'Console' etc.
I have to manually construct a URL to get to the kudu endpoint right now in order to use the console.158 votes
Thanks for bringing this up! This is a known issue and we are working on it. We’ll update the item when complete.
Calling the REST API to get CPU or memory usage of an app service plan, if you ask for it in the last minute it can return 0 to you, when a few minutes later it will return the actual value for the same time, it seems it takes a while for the real data to be available to the API, however I think it's wrong to return incorrect data, it should not return a value until it has the real value.1 vote
We are looking into the details here and will follow up.
Enable surfacing all attributes from Win32_PerfRawData_Tcpip_TCP (https://msdn.microsoft.com/en-us/library/aa394341(v=vs.85).aspx)
We have been experiencing sporadic times of high dependency latency. Understanding where this is coming from would help narrow down a long term solution.
Enable surfacing all attributes from Win32_PerfRawData_Tcpip_TCP https://msdn.microsoft.com/en-us/library/aa394341(v=vs.85).aspx1 vote
We’ll take a look at a possible solution.
- Don't see your idea?