I agree that logging shouldn't be done at the expense of performace but usually that is dictated by how much logging is done and where in the process, not by the logging format. Apache (as an example) seems to be able to cope with high volumes and a readable log file so it can be done.

Having had to cross corelate faults through logs as diverse as unix system logs, firewall-1 logs, apache logs, mail logs, proxy logs, custom application logs etc. my experience has been that having the date time human readable in some recognisable format is essential. I guess I am too much of a Unix guy to want to have to fire up a GUI just to look at an event log :)

--
Until you've lost your reputation, you never realize what a burden it was or what freedom really is. -Margaret Mitchell

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.