XLF: Legacy Log Problems
donpark at quake.net
Thu Jul 9 04:03:44 BST 1998
[ I appologize for not posting this message last night but I literally fell
off my chair and into sleep after posting the Status message. If you are a
workaholic who works til you drop, learn Judo or avoid hardwood floors. <g>]
Let us kick off the first round of discussion by enumerating the problems of
legacy log formats. Please share with the rest of us what you like and/or
hate about log formats you worked with.
WHAT I LIKE:
Logs in ASCII because they are viewable without special tools and because
they can be written out fast.
WHAT I HATE:
Single level of details. I open a web server log and you see zillions of
similar looking entries all with same kind of information. If something
wrong happens to a web server, I would like to see more detailed error
information when and where it happens in the access log.
Custom parsers. Most log formats are simple in structure yet wild in
variety so that custom parsers have to be written for each type of logs your
Non-integrated views. When a server generates multiple log types (i.e.
access, error, etc.), each log types are written out into separate files.
This makes it difficult to analyze problems whose symtoms are spread out
over multiple files. When there are more than one process involved (i.e.
web server, application server, and database server), the task becomes
practically impossible. It would be nice to 'merge' log information from
multiple sources to get a view of the all the components working together.
Let me just stop here so that rest of you have something to write about <g>.
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev