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.
Any update on this request? We have had an issue recently related to this issue that one of the instances went down for some reason (probably due to server failure or planned maintenance, but not due to autoscale rules) and another instance spun up immediately (which is good) but seems load balancer routed requests too early before the new instance was fully ready which caused an outage. Would like to see such a key problem gets addressed soon in a popular cloud platform. Appreciate if this can be expedited to implement as soon as possible. Thanks!
You can now use the Azure CDN to access blobs with custom domains over HTTPS. See the following article for instructions on how to do so: https://docs.microsoft.com/en-us/azure/storage/storage-https-custom-domain-cdn. Having talked to a number of customers, we concluded that this solution addresses many scenarios where the need for HTTPS access to blobs with custom domains exists.
Native Azure Storage support for using SSL to access blobs at custom domains is still on our backlog. We would love to hear about your scenarios where using the Azure CDN is not an acceptable solution, either by posting on this thread or sending us an email at email@example.com.
We are exploring how to implement this feature without compromising privacy. Thank you for all the feedback!
- Matt, Product Manager
Very much needed feature for effective use of App Insights but understand the cost you pay for additional overhead of capturing and storing lot of data so should provide the ability to turn it on/off or do it for failure requests.
Thank you for your feedback. This is one of our top voted items, so this is something we would really like to do. We’re considering this for a future release of Azure Search.
Azure Search Product Team
I understand the nature of re-indexing that needs to prepare data in optimal manner for search. But leaving teams to rebuild indexes for every little changes makes deployment extremely difficult. This is an important feature!
As a workaround, is there technique to speed up index rebuild faster (days into hours)?