Where are the logs that show the errors and events that cause the different actions taken by the platform for recycling instances, adding / removing instances etc?

I recently setup the Scale feature in my Azure Web Service to scale up and down instances based on CPU. This morning I found that the main instance was 'transitioning' and rebooting for some reason. This service has been rock solid until I started configuring the scale feature.

Thanks,

Ryan

• Edited by ryanabr Tuesday, October 15, 2013 3:28 PM

hi Ryan,

Do you use "Diagnostic " in your project? If you use Diagnostic, you could get the log information from the table storage (http://www.windowsazure.com/en-us/develop/net/common-tasks/diagnostics/ ) . if you didn't use it, I suggest you could add this function into your project (NOTE:log file or message need storage space). Also, If you want to view some operation log, I guess you could log on Azure portal, and select "service management", and click "operation log" to view your operation log.Like this pic:

Also, there have some article about "Diagnostics", please refer to:

http://michaelcollier.wordpress.com/2012/04/02/where-is-my-windows-azure-diagnostics-data/

http://stackoverflow.com/questions/10495312/how-to-view-azure-diagnostics-log

>>I recently setup the Scale feature in my Azure Web Service to scale up and down instances based on CPU

Base on my experience, we could get the CPU Rate from the "WADPerformanceTable" , and if we need, we could scaling our instances via Rest API (http://msdn.microsoft.com/en-us/library/windowsazure/ee460809.aspx && http://stackoverflow.com/questions/19197445/how-to-scale-azure-cloud-service-up-and-down-from-rest-api-with-webapi).

Hope it helps!

If I am misunderstanding, please let me know.

Thanks

This kind of answers my question, the Operations Logs were what I was looking for. I was hoping for more detail there as I had a service 'recycle' yesterday and restart and I wanted to know why, but I don't see an event in the logs at the time that it happened to answer my question.

Hi Ryan,

I guess the reason is auto-scale. When we use auto-scale, if metric CPU drops below the our setting target range, an instance will be removed, and if it exceeds the target range an instance would be added.  SO, some instances state will be changed. If you want to view the log information,this video( http://channel9.msdn.com/Shows/Cloud+Cover/Episode-114-Windows-Azure-Autoscale-Alerts-and-Operational-Logs) and this blog (http://weblogs.asp.net/scottgu/archive/2013/06/27/windows-azure-general-availability-release-of-web-sites-mobile-services-new-autoscale-alerts-support-no-credit-card-needed-for-msdn-subscribers.aspx) will help you.

Please try it.

Thanks