I have written a UDPMulticastAppender and integrated it into chainsaw
for just this purpose. We have our dev/qa/vend/prod servers all
broadcasting to separate multicast addresses. We are using nested
diagnostic contexts to tie the transactions back to a specific server (this
is in a multi-node WLS 6.1 environment).
I have also modified Chainsaw to listen for UDP traffic. The port and
multicast address can be configured from the client allowing us to
selectively monitor different environments. The advantage to this
arrangement is that not only can multiple clients monitor the log traffic,
multiple clients can monitor traffic from multiple servers. Since it is
multicast it is also much less demanding on the network infrastructure,
which is important since bandwidth is always limited.
-Gary
----- Original Message -----
From: "Mark Womack" <[EMAIL PROTECTED]>
To: "Log4j-Dev (E-mail)" <[EMAIL PROTECTED]>
Sent: Thursday, March 21, 2002 12:18 PM
Subject: Some thoughts on Chainsaw
>
> 3) The viewer tool should support receiving logging events from multiple
> sources. Currently, Chainsaw only supports setting up one
LoggingReceiver,
> but (I believe) this is just a configuration limitation, not an actual
> limitation. If there were a way to specify it from the gui, it could
easily
> support multiple sources. The messages would be interleaved in the table
> listing of the events, so displaying the event source would be needed.
> Supporting this will allow the debugging of applications that span
multiple
> machines/processes, which are quite common in the world of web
applications
> nowadays. Parallel to this is the ability to add/delete sources
> dynamically, probably via some gui.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
