Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.bbs.mystic    |    Mystic Sysops are mystical nerds...    |    11,842 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 9,961 of 11,842    |
|    g00r00 to All    |
|    Re: BinkP Utility - Stats Generator    |
|    10 May 21 15:10:18    |
      From: nospam.g00r00@f215.n129.z1.fidonet.org               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.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca