TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 809c7bb9   
   REPLY: 1:229/700 aad055b9   
   TZUTC: -0400   
    JE> Something like this would be helpful:   
    JE>    
    JE> Area                     In msgs     Out msgs   Bad Dupe  In bytes   Out   
      
   There are some generic open sourced JAM utilities that produce reports like   
   this but it would't include the dupe stuff and I can't for the life of me   
   remember where to find any of them.   
      
   There may be one or two people who made similar things specifically for Mystic   
   too, but again I don't know what those are I just remember hearing things.   
      
   I can see the IN/OUT messages on a per-base level being a good thing to track   
   and right now it has to come from log parsing MUTIL, so that is one place for   
   some enhancements.  But even if that is tracked internally that still doesn't   
   tell you anything unless you specifically go look.  Maybe what we're really   
   looking for could be some automated notifications when certain things happen?   
      
    JE> I see it as the 1st line of defense of something that may be wrong and   
    JE> point to where to look in the logs instead of having to comb through   
    JE> them.   
      
   If error tracking is your end game then there are some things you may not be   
   aware of, although they are more designed to be   
   hub-based automation features.  Mystic does track things like crash errors,   
   in/out files and bytes via BINKP. You can see all of these stats for each node   
   in the EchoNode Editor whenever you want...   
      
   There is also the "Echo Node Tracker" which will handle all sorts of automated   
   tasks for hubs like resetting stats on time-based intervals, automatically   
   deactivating nodes after periods of inactivity, unsubscribing msg/file bases   
   after automated deactivation, purging outbound packets after inactivity   
   period, automatically swapping from "crash" to hold-type mail delivery after a   
   certain   
   number of days of errors or overall error threshhold, etc.   
      
   But again all of that either happens automatically or requires you to make the   
   effort to go look yourself.  Perhaps we need to build in notifications?   
      
   Open to any ideas of course, if you (or anyone else) has them.   
   --- Mystic BBS v1.12 A47 2021/05/10 (Windows/32)   
    * Origin: Sector 7 | Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 30/0 80/1 90/1 105/81 120/340 457 616 123/10 131 129/215   
   SEEN-BY: 129/305 154/10 30 40 50 700 203/0 218/700 220/80 90 221/6   
   SEEN-BY: 226/30 227/114 201 702 229/101 310 424 426 452 550 664 700   
   SEEN-BY: 229/981 1016 1017 240/1120 5832 249/206 307 317 400 261/38   
   SEEN-BY: 280/464 282/1038 292/854 301/0 1 101 113 317/3 322/757 341/66   
   SEEN-BY: 342/200 633/280 712/848 770/1 3634/12 5020/1042 5058/104   
   PATH: 129/215 154/10 301/1 229/426