Logging in its current state is somewhat useful, but has quite a few limitations. Here are some ideas to enhance the capability of logging.
You can only view/search logs for a single server at a time. Being able to search multiple log files between multiple hosts would be very helpful.
Large log files hang the UI. Sometimes I have long running sessions that create log files 50-100+MB in size. This hangs the UI until RoyalTS loads the entire log file into memory. Is there a way to either prevent that or speed it up? A tool called LTFViewr5u can open HUGE files immediately and allows you to scroll in it just as quickly. I don’t know how it’s done, but it’s amazing!
When duplicating a session, those logs are essentially lost to the UI. I have no way to open them without duplicating the session then loading the dashboard for that duplicate session. This goes the same way for ad-hoc connections. These should either reside under the original non-duplicate connection or somehow be viewable.
Mass export/automatic export of non-ansi version of logs. Unfortunately due to some of the limitations of log files today I resort to opening them outside of RoyalTS. In order for them to be usable I have to manually export to remove the ansi encoding. Could we configure non-ansi versions to be created automatically or allow us to do a mass export?
I realize ansi encoding is used for the playback of sessions, but I almost never actually need to see the real-time playback of a session. Could we actually make this a configurable item?
Easily allow us to purge/cleanup old logs via the UI.