Austin McCollum

My feedback

  1. 348 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Austin McCollum commented  · 

    X-Forwarded-For is very important for the data I work with.

    Austin McCollum supported this idea  · 
  2. 15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Austin McCollum commented  · 

    Any consideration of porting the conversion, formatting functions from LogParser 2.2? I use Log Parser Studio heavily, and it would be great to have certain functions like TO_LOWERCASE(), EXTRACT_PREFIX, EXTRACT_TOKEN.

    Some examples of data that is difficult to read without these formatting functions:
    IIS log "cs-uri-stem" field

    /OWA/14.2.328.9/ClientBin/OwaSl.xap
    /owa/14.2.328.9/scripts/premium/blank.htm
    /owa/14.2.328.9/scripts/premium/cdayvw.js
    /owa/14.2.328.9/scripts/premium/fedmtinv.js
    /owa/14.2.328.9/scripts/premium/fedtcali.js
    ...

    I really would love results that just tally results between the first two "/", for example in LogParser I can use the following formatting functions
    Select TOP 10 TO_LOWERCASE(EXTRACT_TOKEN( cs-uri-stem ,1, '/' )) AS Path

    for results like this:

    Path Total
    rpc 6021529
    ews 119456
    powershell 13795
    autodiscover 3247
    mapi 2304
    owa 1907
    ecp 891
    microsoft-server-activesync 834
    favicon.ico 11
    oab 6

    Then of course, like OMS, Log Parser Studio makes it easy to create a bar chart for visualization.

    Austin McCollum supported this idea  · 

Feedback and Knowledge Base