i wasnt able to get apache::parselog to work
From this comment and your data sample, I have to guess that you aren't using a standard log format, right? Can you show us a sample of your log data and/or the CustomLog directive you use in your Apache configuration? Without that, we can't help you slice and dice it in Perl.
is there a simple way with perl to parse the file and have the ability to pass a file name as an argument?
Yes. Something like the following might work well enough for you depending, of course, on what you haven't told us yet...
#!perl -lan
BEGIN {
$SUM = $N = 0;
$file = shift;
}
if ($F[1] eq $file) {
my ($secs) = ($F[2] =~ /^(\d+)/);
$SUM += $secs; $N++
}
END {
print "Average: " , $SUM/ $N;
}
Put that in a file and run it with two arguments, the full pathname of the file you want stats on and the pathname of the file your parsed log data (i.e. the sample you provided) is in. Something like:
perl get_stats /manual/misc/perf-tuning.html log.data
-sauoq
"My two cents aren't worth a dime.";
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|