ETail - A tail like monitor for chat.log
Entropia tail is a monitoring tool for the chat. It can read and filter in real time the log and do some actions to alert the user if the string searched is found.
Ussually when I'm sweating, or hunting or chatting I don't read the messages in the other chats and then the mob is dry or I've lost somme offer or my weapon is wasted before I noticed it. I've checked some log monitoring tools, real nice tools, but either too complex, like logExpert, or they haven't all all the things I wanted So I decided to try and do one for a not really concentrated player like me.
The program isn't finished yet, and some cool features like searching for trading offers or exporting the results into csv or json aren't finished yet, but the alert and monitor features are totally functional. ATM you can define a filter (regular expressions are acepted) and if the string is matched you can define the following behaviours:
-Set a color for the line found, useful using two screens.
-Hide a line.
-Play a sound using a wave file.
-Read a user defined text usig the TTS of the OS, (I find this one really useful since you can write down wht the computer will say if the string is found)
-Print an alert into the program window.
Also the filters used can be saved and loaded for each activity, the lines found can be saves into a text file for later processing and the log is rotated every 5MB (this was forced by my mistake selecting the programing language HTA/VBScript).
CURRENT VERSION: 0.09 alpha.
No size limit in chat.log. No log rotation available by now, it will be introduced as an option in the last update before the beta version. Advanced filters are unchanged.
Outdated, kept for older versions users (if any).
==============================================================================
IMPORTANT NOTICE ABOUT ROTATING LOGS
==============================================================================
Due the limited file support of VBScript large files (more than 5MB, about 50k lines) will overload the processor, to prevent this the program will automatically rotate the log and compress the original file in a zip file with the following name format "logfilename_DATE_TIME.zip" in the same folder.
The script will promp for the method of rotation. The reencoding method (answer yes to the prompt) is slower but it will correct any encoding fault and remove any blank (chr(0)) characters, also the resulting logfile will be bigger because it is using Unicode instead of ASCII characters.
Answering "No" to the prompt will just copy and zip the log file, but if it has any character encoding errors, they will not be corrected.
Note that if you reencode the log probably you may indicate to any other processing programs that the charset is Unicode UTF-8. If you didn't reencode the log, maybe you will need to correct any faults, like eliminating blank chars.
==
Recovering a failed attempt to rotate.
Before the compression start, the original log is moved to a temporary work file, named with this pattern "logfilename_DATE_TIME.tmp". This file can be renamed safely to "logfilename_DATE_TIME.log" and then saved in another place, note that this file isn't converted.
==
Entropia tail is a monitoring tool for the chat. It can read and filter in real time the log and do some actions to alert the user if the string searched is found.
Ussually when I'm sweating, or hunting or chatting I don't read the messages in the other chats and then the mob is dry or I've lost somme offer or my weapon is wasted before I noticed it. I've checked some log monitoring tools, real nice tools, but either too complex, like logExpert, or they haven't all all the things I wanted So I decided to try and do one for a not really concentrated player like me.
The program isn't finished yet, and some cool features like searching for trading offers or exporting the results into csv or json aren't finished yet, but the alert and monitor features are totally functional. ATM you can define a filter (regular expressions are acepted) and if the string is matched you can define the following behaviours:
-Set a color for the line found, useful using two screens.
-Hide a line.
-Play a sound using a wave file.
-Read a user defined text usig the TTS of the OS, (I find this one really useful since you can write down wht the computer will say if the string is found)
-Print an alert into the program window.
Also the filters used can be saved and loaded for each activity, the lines found can be saves into a text file for later processing and the log is rotated every 5MB (this was forced by my mistake selecting the programing language HTA/VBScript).
CURRENT VERSION: 0.09 alpha.
No size limit in chat.log. No log rotation available by now, it will be introduced as an option in the last update before the beta version. Advanced filters are unchanged.
Outdated, kept for older versions users (if any).
==============================================================================
IMPORTANT NOTICE ABOUT ROTATING LOGS
==============================================================================
Due the limited file support of VBScript large files (more than 5MB, about 50k lines) will overload the processor, to prevent this the program will automatically rotate the log and compress the original file in a zip file with the following name format "logfilename_DATE_TIME.zip" in the same folder.
The script will promp for the method of rotation. The reencoding method (answer yes to the prompt) is slower but it will correct any encoding fault and remove any blank (chr(0)) characters, also the resulting logfile will be bigger because it is using Unicode instead of ASCII characters.
Answering "No" to the prompt will just copy and zip the log file, but if it has any character encoding errors, they will not be corrected.
Note that if you reencode the log probably you may indicate to any other processing programs that the charset is Unicode UTF-8. If you didn't reencode the log, maybe you will need to correct any faults, like eliminating blank chars.
==
Recovering a failed attempt to rotate.
Before the compression start, the original log is moved to a temporary work file, named with this pattern "logfilename_DATE_TIME.tmp". This file can be renamed safely to "logfilename_DATE_TIME.log" and then saved in another place, note that this file isn't converted.
==
Last edited: