My belief is that any logging standard needs a way for a programmer to say *why* a piece of data is being logged, in addition to the severity, timestamp, etc. For example:- *) alerts - eg process death *) accounting data (user has used 17 MB of network bandwidth this session) *) data that is significant above a threshold (eg 5 failed logins (within last hour???) on account xxxxx) *) information that should be expected with a fair degree of regularity (eg 100 HTTP requests completed) *) debugging data *) or plain old "for your information" stuff. If this can be captured, instead of trying to re-create it........ Dan _______________________________________________ LogAnalysis mailing list LogAnalysisat_private https://lists.shmoo.com/mailman/listinfo/loganalysis
This archive was generated by hypermail 2b30 : Wed Aug 21 2002 - 14:50:14 PDT