为什么我的IIS日志被复制我的Azure Web角色？ [英] Why aren't my IIS Logs being copied for my Azure web role?

问题描述

这是<一个跟进href=\"http://stackoverflow.com/questions/15501473/do-i-have-to-redeploy-an-azure-web-role-to-turn-on-iis-logging/15502243\">this问题。我用Cerebrata诊断管理器远程诊断，试图打开IIS日志。我没有上部署它。它似乎工作和一些文件被复制。然后，它似乎从来没有再工作。我再次调整设置。我试着删除IIS相关的BLOB和表存储的条目，看看是否会得到它的开始。这里是配置样子在弹塞控制容器显示，似乎基于Cerebrata工具进行更新。

This is a follow up on this question. I used Cerebrata Diagnostics Manager Remote Diagnostics to try to turn on IIS logs. I hadn't deployed with it on. It seemed to work and a few files were copied. Then it never seemed to work again. I tweaked settings again. I tried deleting the iis related blob and table storage entries to see if that would get it to start over. Here is what the config looks like in the wad-control-container that shows that it seemed to be updated based on Cerebrata tool.

<?xml version="1.0"?>
<ConfigRequest xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <OnDemandTransfers />
  <DataSources>
    <OverallQuotaInMB>4096</OverallQuotaInMB>
    <Logs>
      <BufferQuotaInMB>1024</BufferQuotaInMB>
      <ScheduledTransferPeriodInMinutes>1</ScheduledTransferPeriodInMinutes>
      <ScheduledTransferLogLevelFilter>Undefined</ScheduledTransferLogLevelFilter>
    </Logs>
    <DiagnosticInfrastructureLogs>
      <BufferQuotaInMB>0</BufferQuotaInMB>
      <ScheduledTransferPeriodInMinutes>0</ScheduledTransferPeriodInMinutes>
      <ScheduledTransferLogLevelFilter>Undefined</ScheduledTransferLogLevelFilter>
    </DiagnosticInfrastructureLogs>
    <PerformanceCounters>
      <BufferQuotaInMB>0</BufferQuotaInMB>
      <ScheduledTransferPeriodInMinutes>0</ScheduledTransferPeriodInMinutes>
      <Subscriptions />
    </PerformanceCounters>
    <WindowsEventLog>
      <BufferQuotaInMB>0</BufferQuotaInMB>
      <ScheduledTransferPeriodInMinutes>0</ScheduledTransferPeriodInMinutes>
      <Subscriptions />
      <ScheduledTransferLogLevelFilter>Undefined</ScheduledTransferLogLevelFilter>
    </WindowsEventLog>
    <Directories>
      <BufferQuotaInMB>0</BufferQuotaInMB>
      <ScheduledTransferPeriodInMinutes>1</ScheduledTransferPeriodInMinutes>
      <Subscriptions>
        <DirectoryConfiguration>
          <Path>C:\Resources\directory\8973cd09642f4dfeafe830612cc8c1fe.AllRole.DiagnosticStore\FailedReqLogFiles</Path>
          <Container>wad-iis-failedreqlogfiles</Container>
          <DirectoryQuotaInMB>1024</DirectoryQuotaInMB>
        </DirectoryConfiguration>
        <DirectoryConfiguration>
          <Path>C:\Resources\directory\8973cd09642f4dfeafe830612cc8c1fe.AllRole.DiagnosticStore\LogFiles</Path>
          <Container>wad-iis-logfiles</Container>
          <DirectoryQuotaInMB>1024</DirectoryQuotaInMB>
        </DirectoryConfiguration>
        <DirectoryConfiguration>
          <Path>C:\Resources\directory\8973cd09642f4dfeafe830612cc8c1fe.AllRole.DiagnosticStore\CrashDumps</Path>
          <Container>wad-crash-dumps</Container>
          <DirectoryQuotaInMB>1024</DirectoryQuotaInMB>
        </DirectoryConfiguration>
      </Subscriptions>
    </Directories>
  </DataSources>
  <IsDefault>false</IsDefault>
</ConfigRequest>

这是为什么似乎没有将任何想法来工作？

Any ideas on why it won't seem to work?

更新

我们今天重新部署具有以下diagnostics.wadcfg仍然没有IISLogs。跟踪日志工作。我们没有任何code，因为这是我的理解是该文件可以处理所有调用诊断。我缺少的东西吗？

We redeployed today with the following diagnostics.wadcfg and still no IISLogs. Trace logs are working. We don't have any code that calls the diagnostics because it was my understanding that the file could handle it all. Am I missing something?

<DiagnosticMonitorConfiguration xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration"
      configurationChangePollInterval="PT1M"
      overallQuotaInMB="4096">
  <Logs bufferQuotaInMB="1024"
     scheduledTransferLogLevelFilter="Verbose"
     scheduledTransferPeriod="PT1M" />
  <Directories bufferQuotaInMB="1024"
   scheduledTransferPeriod="PT1M">

    <!-- These three elements specify the special directories 
           that are set up for the log types -->
    <CrashDumps container="wad-crash-dumps" directoryQuotaInMB="256" />
    <FailedRequestLogs container="wad-frq" directoryQuotaInMB="256" />
    <IISLogs container="wad-iis" directoryQuotaInMB="256" />

  </Directories>
</DiagnosticMonitorConfiguration>

会不会是网络角色是XS的实例（因为我们只是测试现在）？再次，它的工作一次，但现在似乎是死了。

Could it be that the web roles are XS instances (since we're just testing right now)? Again, it did work once, but seems to be dead now.

推荐答案

一些建议：

1. 放下OverallQuotaInMB成类似4000

1. Lower the OverallQuotaInMB to something like 4000

增加
该目录节点下BufferQuotaInMB为数字（比如1演出）

Increase BufferQuotaInMB under the Directories node to a number (say 1 gig)

下的其他个人目录配额，使他们加起来
在＃2，使东西比BufferQuotaInMB略少
所有的配额（包括整体目录和和
个人文件夹是OverallQuotaInMB下）。 IE浏览器：原木 - 1GIG
（这是跟踪数据），目录：1演出，FailedRequests：256MB，
IISLogs：256MB，CrashDumps：256MB

Lower the other individual Directory quotas so that they add up to something slightly less than BufferQuotaInMB in #2 and so that ALL of the quotas (including the overall Directories and and individual Folders are under OverallQuotaInMB). IE: Logs - 1gig (this is trace data), Directories: 1 gig, FailedRequests: 256mb, IISLogs: 256mb, CrashDumps: 256mb

重新启动服务器（以防
情况）

Reboot your servers (just in case)

好运气

基本上，我已经看到了当时的平均配额设置为Azure的分配用于诊断存储（4gig）最大空间诊断行动挑剔。降低个人的配额，使他们加起来的金额低于配额总量也帮助，因为如果Azure诊断曾经填满了，有喘息的余地Azure中删除旧数据之前。

Basically, I've seen diagnostics act fussy when the overall quota is set to the max space that Azure allocates for diagnostics storage (4gig). Lowering individual quotas so that they add up to something less than total quota also helps because if Azure Diagnostics ever fills up, there is breathing room before Azure removes old data.

总之，建立Azure诊断是一个黑魔法艺术。我一直在帮助客户AzureWatch了两年，现在做到这一点，我仍然觉得我的配额摸索。希望他们只是让用户打开的事情或关闭对整个配置按照惯例对配置来驱动。几乎没有人关心过的数据捕获到他们的虚拟机，而不是转移到Azure存储，因此小的配额是大多数情况下是完全正常的广大乡亲的数据转移到存储每隔几分钟。

Overall, setting up Azure Diagnostics is something of a black magic art. I've been helping AzureWatch customers do this for two years now and I still feel like I'm fumbling with the quotas. Wish they would just let users turn the thing on or off have the entire config be driven by convention vs. configuration. Almost noone ever cares to capture the data onto their VM's and not transfer it to azure storage and thus small quotas are totally fine for majority of the cases as majority of folks transfer their data to storage every few minutes.

心连心

这篇关于为什么我的IIS日志被复制我的Azure Web角色？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！