Hi,
I'm going to evaluate Logrep for analysing our IIS Logfiles. We have customers paying for traffic. So we configure the websites to log incoming and outgoing bytes.
My question: Is Logrep capable of analyse those custom log files? They specify the fields in their header which looks like this:
#Software: Microsoft Internet Information Services 5.0
#Version: 1.0
#Date: 2006-03-07 00:00:28
#Fields: date time c-ip cs-username s-sitename s-computername s-ip s-port cs-method cs-uri-stem cs-uri-query sc-status sc-win32-status sc-bytes cs-bytes time-taken cs(User-Agent) cs(Referer)
2006-03-07 00:00:28 192.168.102.3 - W3SVC1 DEVELOP-21 83.221.236.78 80 GET /hartung.a/sportresult_neu/sports/la/framework/eaa.asp event_id=10000100000024&comp_id=18435&show=SL&module=competition&lang=en&x-autoreload=1 401 5 4879 1368 0 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.0.3705;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) http://develop-21.wige-data.de/hartung.a/sportresult_neu/sports/la/frame...
2006-03-07 00:00:28 192.168.102.76 - W3SVC1 DEVELOP-21 192.168.102.76 80 GET /hartung.a/sportresult_neu/sports/la/framework/eaa.asp event_id=10000100000024&comp_id=18435&show=SL&module=competition&lang=en&x-cache=1 401 5 4860 408 0 - -
.
.
.
I had a look into module-iis.pl and it seems you require a static log file layout. Does this mean Logrep only regards the fields
$month, $day, $hour, $minute, $to, $method, $document, $port, $user, $from, $result ?
Best regards, Sebastian
Logrep supports the default IIS 6 format:
However, implementing a customized parsing module is not a big deal. Since IIS6 log files contain information about the log file structure, it would be convenient to develop a dynamic iis module. I take it as a feature request.