IIS Advanced Logging 1.0 FeedbackRSS

5 replies

Last post Aug 04, 2011 11:28 AM by sonrounin

  • IIS Advanced Logging 1.0 Feedback

    Oct 12, 2009 06:19 PM|vsood|LINK

    Please use this thread to provide feedback on IIS Advanced Logging 1.0 release. We look forward to your input!

    Advanced Logging Sample Client Firefox Chrome

  • Re: IIS Advanced Logging 1.0 Feedback

    Jul 21, 2011 03:10 PM|jbruns2011|LINK

    Would be nice to see Powershell commands or ways using Powershell to change or set any value or feature that you can with the Advanced Logging GUI.

     If I have 1000 servers to set this up on, I need to do it with a non-GUI process and I do NOT want to pay for a WISE license to do it either.

  • Re: IIS Advanced Logging 1.0 Feedback

    Jul 21, 2011 04:04 PM|Uk-Sam|LINK

    Yes there are multiple post/requirement for managing via powershell.

  • Re: IIS Advanced Logging 1.0 Feedback

    Jul 21, 2011 09:54 PM|CarlosAg|LINK

    You should be able to use the IIS PowerShell module for that, or even simpler use AppCmd, for example:

    appcmd.exe set config "example.com" -section:system.webServer/advancedLogging/server /+"logDefinitions.[baseFileName='MyCustomLog',enabled='False',logRollOption='Schedule',schedule='Hourly',publishLogEvent='False']" /commit:apphost

    appcmd.exe set config "example.com" -section:system.webServer/advancedLogging/server /+"logDefinitions.[baseFileName='MyCustomLog'].selectedFields.[id='Win32Status',logHeaderName='sc-win32-status']" /commit:apphost

    appcmd.exe set config "example.com" -section:system.webServer/advancedLogging/server /+"logDefinitions.[baseFileName='MyCustomLog'].selectedFields.[id='UserName',logHeaderName='cs-username']" /commit:apphost

    appcmd.exe set config "example.com" -section:system.webServer/advancedLogging/server /+"logDefinitions.[baseFileName='MyCustomLog'].selectedFields.[id='URI-Stem',logHeaderName='cs-uri-stem']" /commit:apphost

    appcmd.exe set config "example.com" -section:system.webServer/advancedLogging/server /+"logDefinitions.[baseFileName='MyCustomLog'].selectedFields.[id='URI-Querystring',logHeaderName='cs-uri-stem']" /commit:apphost

    appcmd.exe set config "example.com" -section:system.webServer/advancedLogging/server /+"logDefinitions.[baseFileName='MyCustomLog'].selectedFields.[id='Substatus',logHeaderName='sc-substatus']" /commit:apphost

  • Re: IIS Advanced Logging 1.0 Feedback

    Jul 22, 2011 07:26 AM|jbruns2011|LINK

    I heard appcmd was/is being deprecated, so Powershell or bust.
  • Re: IIS Advanced Logging 1.0 Feedback

    Aug 04, 2011 11:28 AM|sonrounin|LINK

    I've been trying to get a normal instance of Daily logging to work. Although my understanding of what is normal may be completely bizarro. My assumption of daily logging is follows:

    Desired Behavior
    exMMDDYYYY.log - I should be able to fully customize the file name and tell it how often it should it log and what it should log. For instance, a Daily log should only created 1 log per day, like a normal person would expect; an Hourly log, 1 log per hour. You get the idea.

    Actual Behavior
    ex_D20110729-151513910.log - The "ex" is my custom format preface. I would like to remove the underscore and the D. What exactly is the extra string of numbers after the date stamp and why when set to Daily logging does it continually fill up the directory with log files when it could just as easily append to an existing log file? At least give me the option.

    Within a span of a few hours I have this following list of 1k logs:

    ex_D20110802-131916621
    ex_D20110802-131608184
    ex_D20110802-131856731
    ex_D20110802-143306590
    ex_D20110802-143305637
    ex_D20110802-145745043
    ex_D20110802-152715043
    ex_D20110802-152716668
    ex_D20110802-152229856