How can I increase the Diagnostics overallquotainMB > 4096 using the diagnostics configuration file and development storage?

Answered How can I increase the Diagnostics overallquotainMB > 4096 using the diagnostics configuration file and development storage?

  • Thursday, February 17, 2011 9:34 PM
     
      Has Code

    Hello,

    I'm trying to use the diagnostics configuration file (diagnostics.wadcfg) to configure diagnostics from the start. While using development storage I'm unable to increase the overallquotainMB to anything greater than 4096.

    When I increase the OverallQuotainMB to anything over 4097 I get an error "Windows Azure Diagnostics Agent has stopped working" and the diagnostics configuration fails to load.

    I'm not looking for the programmatic approach towards configuring diagnostics but rather using the configuration file to set this from the start.

    <DiagnosticMonitorConfiguration xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration"
    configurationChangePollInterval="PT1M"
    overallQuotaInMB="4096">
     <DiagnosticInfrastructureLogs bufferQuotaInMB="256"
      scheduledTransferLogLevelFilter="Verbose"
      scheduledTransferPeriod="PT1M" />
     <Logs bufferQuotaInMB="256"
       scheduledTransferLogLevelFilter="Verbose"
       scheduledTransferPeriod="PT1M" />
     <Directories bufferQuotaInMB="512"
        scheduledTransferPeriod="PT1M">
      <CrashDumps container="wad-crash-dumps" directoryQuotaInMB="128" />
      <FailedRequestLogs container="wad-frq" directoryQuotaInMB="128"/>
      <IISLogs container="wad-iis" directoryQuotaInMB="128" />  
     </Directories>
     <PerformanceCounters bufferQuotaInMB="256" scheduledTransferPeriod="PT1M">
      <PerformanceCounterConfiguration
        counterSpecifier="\Processor(_Total)\% Processor Time" sampleRate="PT5S" />
      <PerformanceCounterConfiguration
        counterSpecifier="\LogicalDisk(*)\% Free Space" sampleRate="PT5S" />
      <PerformanceCounterConfiguration
        counterSpecifier="\LogicalDisk(*)\Avg. Disk sec/Transfer" sampleRate="PT5S" />
      <PerformanceCounterConfiguration
        counterSpecifier="\Memory\Available Bytes" sampleRate="PT5S" />
      <PerformanceCounterConfiguration
        counterSpecifier="\TCPV4\Segments Retransmitted/sec" sampleRate="PT5S" />
      <PerformanceCounterConfiguration
        counterSpecifier="\TCPV4\Connection Failures" sampleRate="PT5S" />
      <PerformanceCounterConfiguration
        counterSpecifier="\TCPV6\Segments Retransmitted/sec" sampleRate="PT5S" />
      <PerformanceCounterConfiguration
        counterSpecifier="\TCPV6\Connection Failures" sampleRate="PT5S" />
     </PerformanceCounters>
     <WindowsEventLog bufferQuotaInMB="256"
      scheduledTransferLogLevelFilter="Verbose"
      scheduledTransferPeriod="PT1M">
      <DataSource name="System!*" />
      <DataSource name="Application!*"/>
      <DataSource name="Security!*"/>
     </WindowsEventLog>
    </DiagnosticMonitorConfiguration>
    

    dcazares

All Replies

  • Monday, February 21, 2011 11:14 PM
     
     Answered

    When the role starts the Diagnostic Store size is set to default 4096MB by default and the VM is configured to have a FIXED quota for folder name C:\Resources\Directory\*.DiagnosticStore. Once VM is configured to have this FIXED quota you cannot change it in any way. If you really want to modify this size then you will need to change the DiagnosticStore  storage size in the CSDEF file as below and redeployed the service:

        <LocalResources>

          <LocalStorage name="DiagnosticStore" cleanOnRoleRecycle="false" sizeInMB="8192" /> ç Setting 8GB DiagnosticStore

        </LocalResources>


    bill boyce
    • Proposed As Answer by billb08 - MSFT Monday, February 21, 2011 11:14 PM
    • Marked As Answer by dcazares Friday, February 25, 2011 10:49 PM
    •