www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "#asfinfra IRC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-2895) Offer web log analysis
Date Tue, 29 May 2012 05:55:23 GMT

    [ https://issues.apache.org/jira/browse/INFRA-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284623#comment-13284623
] 

#asfinfra IRC Bot commented on INFRA-2895:
------------------------------------------

<danielsh> Please introduce yourself on infra@ to discuss your plans

                
> Offer web log analysis
> ----------------------
>
>                 Key: INFRA-2895
>                 URL: https://issues.apache.org/jira/browse/INFRA-2895
>             Project: Infrastructure
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Website
>            Reporter: Henri Yandell
>            Assignee: Henri Yandell
>
> For the static websites, offer some kind of analysis view to avoid everyone having to
hook in google analytics.
> Vadim used to offer this:
> http://people.apache.org/~vgritsenko/stats/projects/harmony.html
> and Henk has a very high level version, mostly of use to the httpd admin:
> http://people.apache.org/~henkp/analog/
> Demos of other options:
> http://www.nltechno.com/awstats/awstats.pl?config=destailleur.fr
> http://demo.openwebanalytics.com/owa/
> http://demo.piwik.org/index.php?module=CoreHome&action=index&idSite=1&period=week&date=today#module=Dashboard&action=embeddedIndex&idSite=1&period=week&date=today
> http://www.w3perl.com/demo/web/
> Aim would be to run the log files through in some batch mode (daily, weekly, something)
by vhost and therefore offer each TLP their own analysis setup. 
> Steps:
> 1) Figure out what Vadim was doing. I'm not sure if it meets my needs, which is to see
which pages get hit and how often on www.apache.org. 
> 2) Examine the 4 open source packages above for features or take referrals.
> 3) Test out the preferred options, consider cpu usage, general security/pain, simplicity
of maintenance and speed.
> 4) Deploy etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message