++, although "Time Served" seems to point me into thinking the OP wants to know average time "viewed" per URL or some such. In this case the problem becomes a little more difficult, HTTP is a stateless protocol where you can't really tell that a user is on the same page from lasthit -> thishit in the log. You can define what you consider a page view duration with the last fact accepted, you just have to define it for yourself -- it does not really "mean" anything in the real world.

So to do a view duration you need a session of some type (based on key fields like client IP, timestamp and others in the log) or better yet a real session ID in the log that tells you for sure this is the same session -- not someone else on the same proxy server. After you have that defined you need to suck in the log and make a correlation between sessionID_last_hit and sessionID_next_hit The time that elapses between those two is the "viewed" time for the "SessionID_last_hit" page. Note you will want to have tests for outlying hits (what if the user started on index.html at 1pm yesterday, then started on page2.html today at 1pm, is that a 24hour view?) and do sanity cleaning on those cases. For examples of how some people have implemented this take a look at awstats.


-Waswas

In reply to Re: Re: apache log parsing by waswas-fng
in thread apache log parsing by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.