Glen, My goal is to not be tied up to any particular tool but rather use a log format acceptable by popular logfile analyzers. It was suggested to me that I start out with something like Apache CLF (Common Log Format) and support other formats in the future (see comments in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11737). I believe that CLF is supported both WebTrends and Analog (I still have to test). Someone on the mailing list already tried a sample log I posted with Webalizer.
Initial implementation is very simple - CLF only. Fully customizable log entry format will be a future enhancement. It would be nice to determine the request size in bytes but I haven't looked into it yet - not sure if that is even possible without a lot of overhead. Best regards, Mark C. Orciuch Next Generation Solutions, Ltd. e-Mail: [EMAIL PROTECTED] web: http://www.ngsltd.com > -----Original Message----- > From: Glen Carl - CSC [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, August 27, 2002 11:51 AM > To: Jetspeed Developers List > Subject: Re: cvs commit: jakarta-jetspeed/proposals > PortletUsageLogging.txt > > > In addition to WebTrends format would you also create a format supported > by Analog, http://www.analog.cx/ or better yet Report Magic, > http://www.reportmagic.org/ ? > > Thanks, > Glen > > [EMAIL PROTECTED] wrote: > > morciuch 2002/08/27 08:37:13 > > > > Added: proposals PortletUsageLogging.txt > > Log: > > Initial check in (see Bugzilla issue 11737) > > Approach > > ======== > > > > My proposed approach is to create a Turbine service > responsible for managing the portlet usage statistcs. The call to > this service's logAccess() method would be the "implanted" in > appropriate places where portle content is requested. The most > logical choice for the the logging engine is log4j. The following > are main features of the feference implementation: > > > > 1. Log entry to utilize the Common Log Format for ease of > integration with WebTrends (or similar tool). > > 2. Lightweight implementation of the logAccess method so it > won't affect performance. > > 3. Current stats cache (optional). > > 4. Methods to return current stats from the cache - by > portlet and by user (optional). > > 5. Administrative portlet to display current stats (optional). > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
