Well, chainsaw already acts as a prety good socket listener. But if I
understand you correctly, you want the socket listener itself to then re-log
messages to various sources? Why not just have this done in the first place,
rather than going thorugh the overhead of relogging the same messages?
Anyway, chainsaw link is here: http://www.geocities.com/oburn/chainsaw/
sam
----- Original Message -----
From: "Alain RAVET" <[EMAIL PROTECTED]>
To: "LOG4J Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, July 30, 2001 8:38 AM
Subject: SocketAppender based filtering relay/router..
> Hi all,
>
>
> We plan to use log4j for the monitoring of remote applications.
>
> As there will be many clients, we want them to log to a SocketAppender, an
> have the server (socket listener) make the routing/filtering the log
> messages decisions, based on simple rules.
>
> We'd thought about building a socket listener to handle the messages,
> depending on their contents, source, priority.
> We need to
> - display in a terminal all the live messages,
> - log all the received messages in a DB,
> - route some messages based on some rules
> (ex. when a WARNING comes in, send an email to ..)
> (ex. when a ERROR comes in, send a SMS to ..)
> - ...
>
> Does anything like this already exists?
>
> Thanks in advance.
>
>
> Alain Ravet
> Brussels, Belgium
>
>
> This mail has been checked by exiscan.
> To be safe, please scan the mail attachements with your local virus
scanner !
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
