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.
I have searched as well and found nothing. I will keep looking
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've been to all the Mystic related sites I can find and none seem to have anything for stats on message bases, everything else though!
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?
I hear you on going to look. I prefer to get a report of what the system is doing and if I see something in the report, yes, go look. But with a large amount of message bases and networks, its too much to look though the log for potential problems. Maybe its the reports I am used to in my job that brings this to mind. With all the telemetry that gets recorded for our fleet of trucks, I simply can't just go look for issues. I need those reports to point me to potential issues so I know where to look.
Had an issue the other day with 1 hub and if I didn't happen to be scrolling through the message bases I would never have found it as I don't read that peticular base. Saw that an enormous amount of messages were arriving each
poll to the hub. I am talking 10's of thousands of messages. Investigated an found messages coming in decades old. Emailed the sysop right away and the problem was fixed. Fixed in 1 day. That was just by luck. Reading a report everyday would help so much.
I would be very interested in 'automating' these internal reports you
touched on. They would be very helpful.
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...
I will check this out. No, I was not aware. After I look, I may have some ideas.
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,
I can see where Hubs would use this. Gives me more to look at.:-)
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.
If you don't mind, I do have some ideas that would fit right in with built in notifications.
I have that in my work and my Home streaming server. It notifies when
something isn't working and reports what was happening just before the issue.
I can correct immediately (remotely if needed) to get the streaming server
back online for the family viewers. Better that getting a call from daughter who just says "Its not working and can't watch my show".
Thank you for the information. It is very helpful.
--- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)
* Origin: Mystic Realms - A Social Media Alternative (1:229/700)