Carson Gaspar <[EMAIL PROTECTED]> wrote:
> One correct solution to this is to propogate the timestamp with the
> message, so the propogation delay isn't an issue, and neither are time
> differences between the reporting and logging systems.
Time synchronization can also be accomplished by logging to multiple
hosts. Variances would normally be obvious. Whether or not a timestamp
is propogated a (primary) timestamp should always be logged at the
localhost.
Also the lack of timeZONE info in the timestamp is a common gripe. It
might be worthwhile to add a short field with this info i.e:
991019_12:54:02_GMT+8.
> Time synchronization is _definitely_ outside the scope of a logging
> protocol.
Agreed.
--
Roger Marquis
Roble Systems Consulting
http://www.roble.com/
