On Wed, 24 May 1995, Randy Terbush wrote:
> I prefer the idea of the socket and write *everything* to the listening
> process. Let the logger determine what to do with it.
+1
> 2. I would like to see this group create our own log format. It
> would be easy to provide a logger daemon that converted it to CLF
> and wrote it to a flat file. I would like to see Apache sending
> access dates in integer format and logging the IP address only.
>
> Reducing the output of the present CLF to this.
>
> 198.183.2.1 - - 81100035 GET /man/Perl5/perlfunc.html HTTP/1.0 200 135964
+1 again, with notes:
1) Whatever the separator is, we need to make sure the data escapes that
character - i.e., this has caused problems at hotwired:
198.183.2.1 - brian behlendorf (etc).... 401 -
I would actually prefer to have tabs separate the data, for a couple
reasons:
a) spaces can be preserved (important for user-agent)
b) it's a standard for importing to other databases.
2) I liked Rob Hartil's MIME-ish dump of the mime headers, but it seems
like that will dramatically increase the overhead for a logging daemon
that needs to be sooper efficient. Maybe have a separate extra-credit
pipe for anything our CLF2 doesn't handle.
3) How does this look:
IP RFC931 REMOTE_USER TIME METHOD URI PROTOCOL BYTESTRANSFERRED STATUSRESPONSE SESSIONID REALOBJECT
SERVERNAME REFERRER USERAGENT
where SESSIONID won't be around until 1.1 at least, REALOBJECT is the
canonical object retreived (if it exists - i.e., a get for "mother" returned
"mother.gif"), SERVERNAME is the virtualhost accessed. Anything else we
should be logging?
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com brian@hyperreal.com http://www.[hyperreal,organic].com/
|