portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 11737] - Portlet Usage Logging
Date Mon, 19 Aug 2002 19:20:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11737>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11737

Portlet Usage Logging





------- Additional Comments From franck.lumpe@iberplus.com  2002-08-19 19:20 -------
Mark,

I was checking again your proposal.

>From draft:
>> The following are main features of the reference 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.
>> 4. Methods to return current stats from the cache (by portlet and by user).
>> 5. Administrative portlet to display current stats.

I understand 1. and 2. (log file generation ) but why are features 3. to 5. 
needed?

Maybe it is enough to generate log files for detailed Jetspeed activity because 
Tools as Analog & Webalizer (another free logfile analyzer) generate easy to 
read HTML Reports (see example in 
http://www.statslab.cam.ac.uk/webstats/stats.html)

Typically a batch program is scheduled each night to generate HTML Activity 
Reports based on Logfiles.

I understand a standard HTML portlet could be used to visualize resulting HTML 
report (fixed file) within Jetspeed.

--
To unsubscribe, e-mail:   <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>


Mime
View raw message