Depending on they number of distinct messages that interests, you could have separate appenders for each message (using filters). Depending on the volume you may only want to roll weekly or monthly so that tail would work better. Or you could just have a program that checks the special appenders for an increase in size.
On 5/23/07, Roger Varley <[EMAIL PROTECTED]> wrote:
Hi Is there an appender that will allow me to monitor for a specific message or list of specific messages and allow me to trigger an action against those messages. I may need a different action for each message. Background. I'm supporting a third party java web application. I don't have access to the source code nor am I allowed to de-compile and modify the source code. However, the application is using log4j for it's logging. At the moment I'm manually monitoring the logfiles for the appearance of specific messages and manually taking action based on those messages. I've tried writing a unix like "tail" program to monitor the logfile directly but this fails overnight when the logfile rolls over to a new logfile. So I thought that adding my own appender might be a more elegant solution. I'm quite prepared to have a go at doing this myself but I thought that I would check first in case this has already been done. I'd also be grateful for alternate suggestions if it is generally felt that this is not a good idea. Regards Gilbert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- James Stauffer http://www.geocities.com/stauffer_james/ Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
