How to revert to diagnostics.wadcfg configuration from wad-control-container blob.

Question

Hello all,
In our project at some point in the past we have enabled Diagnostics module for getting our log entries in Azure Storage. We added <Import moduleName="Diagnostics" /> to ServiceDefinition.csdef file and then enabled logs transfering and performance
counters gathering in WebRole.OnStart method via DiagnosticMonitor.Start():
DiagnosticMonitorConfiguration cfg = DiagnosticMonitor.GetDefaultInitialConfiguration();
cfg.OverallQuotaInMB = 8192;
cfg.Logs.ScheduledTransferLogLevelFilter = LogLevel.Verbose;
cfg.Logs.ScheduledTransferPeriod = TimeSpan.FromSeconds(30);
cfg.Logs.BufferQuotaInMB = 1000;
// Define performance counter configuration.
foreach (var counterName in PERFORMANCE_COUNTERS_NAMES)
PerformanceCounterConfiguration perfCounterConfiguration = new PerformanceCounterConfiguration();
perfCounterConfiguration.CounterSpecifier = counterName;
perfCounterConfiguration.SampleRate = TimeSpan.FromSeconds(5);
cfg.PerformanceCounters.DataSources.Add(perfCounterConfiguration);
cfg.PerformanceCounters.BufferQuotaInMB = 1024;
cfg.PerformanceCounters.ScheduledTransferPeriod = TimeSpan.FromMinutes(1);
DiagnosticMonitor.Start("Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString", cfg);
Then using Windows Azure Management Portal we activated Verbose monitoring mode and added several additional performance counters there in order to try the feature. I assume that doing that through the portal we actually modified wad-control-container blob
so we got new performace counters configuration.
Later we've realized that it would be better to manage all diagnostic configuration in diagnostics.wadcfg. We removed the code from role start and added diagnostics.wadcfg file to the project that declares the same we did before via code. When we redeployed
we saw that the configuration remained as it was before - it didn't change at all. It still included new performance counters we added through the portal. It is because the order of precedence, where wad-control-container blob has the highest priority. So
we deleted all the blobs from wad-control-container in order to revert back to diagnostics.wadcfg and redeployed the service. New blob was created in wad-control-container. It included everything from diagnostics.wadcfg as we expected and
again we saw these custom performance counters we added via portal time ago. See below the blob content:
<?xml version="1.0"?>
<ConfigRequest xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DataSources>
<OverallQuotaInMB>8192</OverallQuotaInMB>
<Logs>
<BufferQuotaInMB>1024</BufferQuotaInMB>
<ScheduledTransferPeriodInMinutes>1</ScheduledTransferPeriodInMinutes>
<ScheduledTransferLogLevelFilter>Verbose</ScheduledTransferLogLevelFilter>
</Logs>
<DiagnosticInfrastructureLogs>
<BufferQuotaInMB>1024</BufferQuotaInMB>
<ScheduledTransferPeriodInMinutes>5</ScheduledTransferPeriodInMinutes>
<ScheduledTransferLogLevelFilter>Warning</ScheduledTransferLogLevelFilter>
</DiagnosticInfrastructureLogs>
<PerformanceCounters>
<BufferQuotaInMB>4096</BufferQuotaInMB>
<ScheduledTransferPeriodInMinutes>5</ScheduledTransferPeriodInMinutes>
<Subscriptions>
<PerformanceCounterConfiguration>
<CounterSpecifier>\Memory\Available Mbytes</CounterSpecifier>
<SampleRateInSeconds>10</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\Processor(_Total)\% Processor Time</CounterSpecifier>
<SampleRateInSeconds>10</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\ASP.NET Applications(__Total__)\Requests/Sec</CounterSpecifier>
<SampleRateInSeconds>5</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\ASP.NET Applications(__Total__)\Requests Executing</CounterSpecifier>
<SampleRateInSeconds>5</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\ASP.NET Applications(__Total__)\Requests In Application Queue</CounterSpecifier>
<SampleRateInSeconds>5</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\ASP.NET Applications(__Total__)\Requests Failed</CounterSpecifier>
<SampleRateInSeconds>30</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\ASP.NET Applications(__Total__)\Requests Timed Out</CounterSpecifier>
<SampleRateInSeconds>30</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\ASP.NET\Requests Rejected</CounterSpecifier>
<SampleRateInSeconds>30</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\ASP.NET\Worker Process Restarts</CounterSpecifier>
<SampleRateInSeconds>600</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<!-- OLD unnecessary counters that were added manually through the portal START-->
<PerformanceCounterConfiguration>
<CounterSpecifier>\Memory\Available MBytes</CounterSpecifier>
<SampleRateInSeconds>180</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\Web Service(_Total)\ISAPI Extension Requests/sec</CounterSpecifier>
<SampleRateInSeconds>180</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\Web Service(_Total)\Bytes Total/Sec</CounterSpecifier>
<SampleRateInSeconds>180</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\ASP.NET Applications(__Total__)\Errors Total/Sec</CounterSpecifier>
<SampleRateInSeconds>180</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<PerformanceCounterConfiguration>
<CounterSpecifier>\ASP.NET\Requests Queued</CounterSpecifier>
<SampleRateInSeconds>180</SampleRateInSeconds>
</PerformanceCounterConfiguration>
<!-- OLD unnecessary counters that were added manually through the portal END-->
</Subscriptions>
</PerformanceCounters>
<WindowsEventLog>
<BufferQuotaInMB>0</BufferQuotaInMB>
<ScheduledTransferPeriodInMinutes>0</ScheduledTransferPeriodInMinutes>
<Subscriptions />
<ScheduledTransferLogLevelFilter>Undefined</ScheduledTransferLogLevelFilter>
</WindowsEventLog>
<Directories>
<BufferQuotaInMB>256</BufferQuotaInMB>
<ScheduledTransferPeriodInMinutes>5</ScheduledTransferPeriodInMinutes>
<Subscriptions>
<DirectoryConfiguration>
<Path>C:\Resources\directory\ac17d63416cf41c8acfebbbcb3d90052.Mbo.Services.Web.DiagnosticStore\CrashDumps</Path>
<Container>wad-crash-dumps</Container>
<DirectoryQuotaInMB>256</DirectoryQuotaInMB>
</DirectoryConfiguration>
</Subscriptions>
</Directories>
</DataSources>
<IsDefault>false</IsDefault> <!-- DEFAULT IS SET TO FALSE AGAIN -->
</ConfigRequest>
We tried to directly edit this XML. We removed redundant counters and changed IsDefault to "true" value in the XML and updated the blob in the wad-control-container using Azure Management Studio. Next time we redeployed the service - the counters
again appeared in the configuration and IsDefault reverted to false again.
Does anyone know how to permanently revert to managing diagnostics configuration only via diagnostics.wadcfg file and force the Azure to forget about manual edits we did via the portal?
We use Azure SDK 1.4. 
Thanks in advance for any insights!
Vitaly

Answer 1

Hi Vitaly,
Did you try to change diagnostics configuration in VS? Like this:
I suggest you could click the "Edit", and select your diagnostics metrics. Also, I want you double check your  re-deployment  project whether is right. Please try it.
By the way, I suggest you could upgrade your SDK version and refer to this sample:
http://www.windowsazure.com/en-us/develop/net/common-tasks/performance-profiling/
http://msdn.microsoft.com/en-us/library/windowsazure/hh411542.aspx
Any question or result, please let me know.
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.