|
Tony,
A good option! Thanks. I can do an
impact analysis on this option.
It is frustrating that all the information I need
is already in the apache log files and yet I might have to touch some code that
works just to get reports to look a certain way. :(. Sorry, your
suggestion is right on, I'm just blowing off steam at the products I'm working
with :)
----- Original Message -----
Sent: Friday, January 07, 2005 9:29
AM
Subject: RE: [Juglist] web page access
statistics are misleadingthroughanalyzer tool
David,
If you are running Apache you could use mod_rewrite to
create static URL's which would fix your stats.
For example:
could become:
I don't know if it would require too large of a code
rewrite for you but this is how I do it.
Tony
Anyone on here use Webalizer ( http://www.mrunix.net/webalizer/) for stat tracking on their Web site? We use it on
our company site, but have recently changed URL structure.
Using a command pattern we have one request routing
servlet that all requests go through which causes all the URLs
to start with the same servlet name.
Does anyone know if Webalizer can
differentiate based on parameter values (it doesn't seem to be looking
past the servlet name (i.e. We want to track /gateway?cmd=AboutUs separately
from /gateway?cmd=Home) Currently, all hits are being reported against
just /gateway.
Or, does anyone know of a FREE analysis tool that will
accomplish my goal. My client is perturbed and blaming the Java
technology.
Thanks,
David
_______________________________________________ Juglist mailing
list [email protected] http://trijug.org/mailman/listinfo/juglist_trijug.org
|
_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org