You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org> on 2007/05/22 21:51:59 UTC

[jira] Updated: (MRM-149) create an access log for the proxy

     [ http://jira.codehaus.org/browse/MRM-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joakim Erdfelt updated MRM-149:
-------------------------------

    Fix Version/s:     (was: 1.0)
                   Future

> create an access log for the proxy
> ----------------------------------
>
>                 Key: MRM-149
>                 URL: http://jira.codehaus.org/browse/MRM-149
>             Project: Archiva
>          Issue Type: Task
>          Components: remote proxy
>            Reporter: Brett Porter
>             Fix For: Future
>
>
> currently we just log some information to the standard logger, however the granularity should be improved, and we possibly should track more information such as which repositories it failed from. This could be done with a custom plexus logger, or perhaps a separate interface that stores information by field to be able to search and analyse it without processing the log file.
> We may also want to track traditional user fields such as user agent, ip, etc like a normal access log.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira