Using LogParser 2.2 to Parse IIS Logs and Other Logs: ASP Alliance

Print Add To Favorites Email To Friend Rate This Article
Using LogParser 2.2 to Parse IIS Logs and Other Logs

page 6 of 13

by Sudeep G
Feedback

Average Rating:

Views (Total / Last 10 Days): 89170/ 144

Article Contents:

Introduction
Introducing LogParser
Scenario 1: Common types of outputs
Scenario 2: Filtering
Scenario 3: More filtering
Scenario 4: Combining Fields
Scenario 5: Pattern Matching
Scenario 6: Usage with HTTPErr logs
Scenario 7: Using with FileMon/Regmon output logs
Scenario 8: Using LogParser with EventLogs
Scenario 9: Using LogParser with Netmon Traces
Scenario 10: Parsing and viewing an ETW Trace
Summary

Scenario 4: Combining Fields

Now you wish to trace requests to a specific URL and want to get the protocol status and protocol sub-status combined.

Listing 17

LogParser -i:IISW3C -o:DataGrid "SELECT cs-uri-stem, STRCAT(TO_STRING(sc-status), 
STRCAT('.',TO_STRING(sc-substatus))) as Status FROM ex080620.log" -q:ON 
–o:DataGrid

This will find all requests that failed with a status code of HTTP 500.

Listing 18

LogParser -i:IISW3C -o:DataGrid "SELECT cs-uri-stem,  sc-status as Status FROM  
ex080620.log WHERE Status='500'" -q:ON

« (Page 5)

View Entire Article

(Page 7) »

User Comments

No comments posted yet.

Product Spotlight