As we all know as coders, things like logging are never important. Our code will work right
the first time. So, you can understand my surprise when
the first time I deployed
the autoscaling worker role to
the actual Azure fabric, it did not scale. I mean, it worked on my machine. How dare
the datacenter argue with that. So, how did I track down
the problem? (turns out, it was not so much code as lack of
the right certificate) When I ran it local in
the developer fabric, I was able to see a wealth of information. Lots of periodic status info every time
the autoscalar came around to check on my rules and decide to act or not. But that information was not making it to Azure storage.
The diagnostics were not being transferred to where I could easily see and use them to track down why things were not being cooperative. After a bit of digging, I discover
the problem. You need to add a bit of extra configuration code to get
the correct information stored for you. I added
the following to my app.config: Code Snippet <system.diagnostics> <sources> <source name="Autoscaling General"switchName="SourceSwitch" switchType="System.Diagnostics.SourceSwitch" > <listeners> <add name="AzureDiag" /> <remove name="Default"/> </listeners> </source> <source name="Autoscaling Updates"switchName="SourceSwitch" switchType="System.Diagnostics.SourceSwitch" > <listeners> <add name="AzureDiag" /> <remove name="Default"/> </listeners> </source> </sources> <switches> <add name="SourceSwitch" value="Verbose, Information, Warning, Error, Critical" /> </switches> <sharedListeners> <add type="Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorTraceListener,Microsoft.WindowsAzure.Diagnostics, Version=1.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35" name="AzureDiag"/> </sharedListeners> <trace> <listeners> <add type="Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorTraceListener,Microsoft.WindowsAzure.Diagnostics, Version=1.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35" name="AzureDiagnostics"> <filter type="" /> </add> </listeners> </trace> </system.diagnostics> Suddenly all
the rich tracing info I needed was filling up my storage account. After a few cycles of trying to attempting to scale, I identified
the cert problem, uploaded a correct certificate, and away it went. I hope this was helpful.
