From: nospam.g00r00@f215.n129.z1.fidonet.org   
      
    JE> I have searched as well and found nothing. I will keep looking   
      
   I did some basic searching too and its sad that some of these things are   
   getting lost.   
      
   I'm surprised no one else has jumped in to tell us of them too since I know   
   others have used them in the past.   
      
    JE> large amount of message bases and networks, its too much to look though   
    JE> the log for potential problems. Maybe its the reports I am used to in my   
    JE> job that brings this to mind. With all the telemetry that gets recorded   
    JE> for our fleet of trucks, I simply can't just go look for issues. I need   
    JE> those reports to point me to potential issues so I know where to look.   
      
   For most situations you're not going to need to go through logs but in that   
   situation you described with the old messages yeah that would slip through the   
   cracks.  We need to figure out a way to identify that scenario easier.   
      
   When you go into Echomail nodes you can see the number of days nodes have been   
   inactive, if there is a "streak" of crash errors when attempting to send mail   
   (and how many), the last time data was successfully sent, the last time data   
   was successfully received, the inbound flow byte size and file count, the   
   outbound flow byte size and file count...   
      
   You can see this all reported in real time without needing to generate   
   anything.  I think the issue is that just like you'd be required to generate   
   and review a report, you have to go in and look.  So maybe being able to set   
   parameters that allow you to be notified would be a good first step.   
      
    JE> If you don't mind, I do have some ideas that would fit right in with   
    JE> built in notifications.   
      
   Absolutely I would love to hear it!   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)