Hey Pete: FYI: Spam filters seem to be working exceptionally well the past 2 days. Almost nothing gets through (I've also got my spam route rule set to level20).
Thanks. Rick Robeson getlocalnews.com [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Pete McNeil Sent: Friday, June 04, 2004 1:18 PM To: [EMAIL PROTECTED] Subject: [sniffer] Prototype real time performance monitor and logging - please comment Hello Sniffer Folks, For version 2-3.1 we are creating a real time monitoring system for persistent instances of Message Sniffer. The persistent instance will update a snflicid.perf.now.xml file approximately once per minute (adjustable). This file can be read as needed to monitor the current performance statistics of the email system - or at least the Message Sniffer part of it. This makes it possible to understand the system's performance at a glance and may eliminate the need for heavy log processing. A prototype of the "scorecard" file format is here: http://www.sortmonster.com/MessageSniffer/Demo/snfrv2r3.perf.now.xml (The data in the file is entirely simulated at this point.) Since the file is in xml format it can be readily imported into a database or processed into a real-time web display etc... Also, it will be relatively easy to add elements to the file as new features are added or to accommodate requests for additional statistics. The plan is also to have these records appended to a snflicid.perf.log.xml file so that a running series of performance snapshots can be easily captured - perhaps for later import into a database and/or graphing engines. If you are interested in real time performance statistics then please review the sample file and respond/discuss your thoughts about it in this thread. I will be taking all comments into consideration before finalizing the specifications for the file format. --- additional note: I have used a fixed space format within the xml file so that it can be easily read with an ordinary text editor. As a result, the size of the file would remain constant. Interpreters should not depend on this, however, since this feature may be dropped to save space. --- additional note: Another section will be added to this file format which will count specific error conditions which are encountered by the system. There are a number of low-grade error conditions which occur as a normal consequence of the cellular peer-server protocols. When debugging problems it can be helpful to know that these errors are occurring at acceptable and nominal rates. --- Also: If anyone is interested in taking a stab at a .css file to make the output of this file "pretty" please let us know. Right now I am concentrating on well formed data so it will be some time before I get to any aesthetic work ;-) Thanks, _M Pete McNeil (Madscientist) President, MicroNeil Research Corporation Chief SortMonster (www.sortmonster.com) This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
