Access log for requests
-----------------------
Key: GEOS-1632
URL: http://jira.codehaus.org/browse/GEOS-1632
Project: GeoServer
Issue Type: New Feature
Affects Versions: 1.6.0-RC2
Reporter: Arne Kepp
Priority: Minor
Fix For: 1.7.x
Occassionally GeoServer receives requests that make it consume a lot of resources, to the point that you can't be sure whether the process is hanging or still working on it.
I don't know of a good way to identify these requests, a nice improvement would be to provide the equivalent of an Apache combined access_log, where each line looks like
<ip of client> - - [date - time] - "GET ... request" <HTTP status code> <Size of response> <Referer URL> <User agent>
The major drawback of this solution is that it doesn't cover requests made through posted XML, it will only show the URL to which the request was sent.
We looked into using the Apache Tomcat Valve component, which does provide common and combined logging with a tiny change to Tomcat's configuration file. Unfortunately, it is of no use to us because it only writes to the log after the request completes, which never happens in the cases we are most interested in.
Additionally, it may be desirable to provide a log format that can be interpreted by the many statistical packages available for HTTP servers. The problem with this is that these tools would not be able to interpret the URLs in a meaningful way, the bounding boxes etc. would make most requests look unique. Instead we may want to create an artificial output that changes URLs to look like /service/layer/projection/zoomlevel or something similar, which would be treated as directories by the statistics packages.
--
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