GA does provide a bunch of useful information. What it does not
provide, is analysis of your error log. I find that looking through the
errorlog is useful for fixing holes in the web application, seeing
kiddies sweeping for holes, and if you've got ads, the error log is
useful for seeing how to add additional redirects to monitize your errors.
GA is great for seeing the traffic volume and where people are going,
but there's more stuff in your web logs that GA cannot analyze.
On 2/7/13 12:10 PM, Howard White wrote:
On 02/07/2013 11:06 AM, Chris McQuistion wrote:
This might be a little heretical, but have you considered using Google
Analytics, which involves pasting javascript into your web pages, as
opposed to monitoring Apache, itself?
Not the right solution for everyone, but pretty darn good for some
things.
Chris
This was part of my inquiry, Chris. I have seen (in a very simple
search) that java based analytics versus log analytics give widely
different answers. Hence the advent of AWStats and JAWStats which may
run concurrently.
I accept all discussion. Remarks about Google Analytics are not the
least bit heretical.
Howard
--
Drew from Zhrodague
lolcat divinator
[email protected]
--
--
You received this message because you are subscribed to the Google Groups
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nlug-talk?hl=en
---
You received this message because you are subscribed to the Google Groups "NLUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
