Hi all, I'm found of Log4J for a while, I'm using it anywhere but I'm facing a problem (not really) that I'm unable to resolve with current Log4J code. So this post claims to define a user need & a new feature or admitting that I don't know everything for this great tool.
I'm working in a clustered environnement, with the same apps deployed on several machines..Using the same config file from my application server for log4J I can use a chainsaw console for viewing every trace from my application... But :( how could I distinct any error on the application server 1 with the same problem on the application server 2 ? My customers need really a way to administrate their application servers without using 1 chainsaw / server or without using one config file per server. I would add that the 2nd solution is used as a hack now but I would prefer a way to have the IP or hostname of the sender of the Logging Event. After an in depth look to the log4j architecture I think (may be wrong ?) that this latest class is the perfect way to add this data, eevry appender would be able to use it later... Adding a few lines of code for the PatternLayout & wee could use something like %i or %h for adding IP or hostnames in our traces.... If this architecture sounds good for you & that I don't miss some trivial way to achieve my goals I 'm ready to code this feature & to send you my patches (I can be paid to do this :) ). Your optinions would be greatly appreciated Sorry for my poor english written Cheers Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
