I built an appender that buffers messages and it will write the content to the appender on the stop method. With this appender I want to collect messages that are related to a specific Object instance in my application. For example; I want to collect all messages that belong to one ProcessingRequest. Once this request is completed I want to flush it out to a Space as one string plus host and some more info.... I noticed that the appender does not exist any more after I call the stop method. Furthermore it looks like appenders are not created on a per logger basis, there seems to be just one appender instance .... Is there a way to force a new appender instance for each logger ? Thanks Chris -- View this message in context: http://www.nabble.com/Appender-question-tp23922806p23922806.html Sent from the Logback User mailing list archive at Nabble.com.
I guess it's called SiftingAppender :) The only problem I have now is how to get the actual appender in my application. The SiftingAppender creates appenders named "SPACE-1" SPACE-2 SPACE-3 etc. How can I find my appenders ? I saw some posts they talk about AppenderTracker, how is this used ? I need to flush them and then remove them from the appender list. Thanks Chris muleman wrote:
I built an appender that buffers messages and it will write the content to the appender on the stop method.
With this appender I want to collect messages that are related to a specific Object instance in my application. For example; I want to collect all messages that belong to one ProcessingRequest. Once this request is completed I want to flush it out to a Space as one string plus host and some more info....
I noticed that the appender does not exist any more after I call the stop method. Furthermore it looks like appenders are not created on a per logger basis, there seems to be just one appender instance ....
Is there a way to force a new appender instance for each logger ?
Thanks Chris
-- View this message in context: http://www.nabble.com/Appender-question-tp23922806p23926926.html Sent from the Logback User mailing list archive at Nabble.com.
Problem solved Would be nice if the getAppenderTracker method is public public class SiftingAppender extends SiftingAppenderBase<LoggingEvent> { AppenderTracker<LoggingEvent> getAppenderTracker() { return appenderTracker; } muleman wrote:
I guess it's called SiftingAppender :)
The only problem I have now is how to get the actual appender in my application. The SiftingAppender creates appenders named "SPACE-1" SPACE-2 SPACE-3 etc.
How can I find my appenders ? I saw some posts they talk about AppenderTracker, how is this used ? I need to flush them and then remove them from the appender list.
Thanks Chris
muleman wrote:
I built an appender that buffers messages and it will write the content to the appender on the stop method.
With this appender I want to collect messages that are related to a specific Object instance in my application. For example; I want to collect all messages that belong to one ProcessingRequest. Once this request is completed I want to flush it out to a Space as one string plus host and some more info....
I noticed that the appender does not exist any more after I call the stop method. Furthermore it looks like appenders are not created on a per logger basis, there seems to be just one appender instance ....
Is there a way to force a new appender instance for each logger ?
Thanks Chris
-- View this message in context: http://www.nabble.com/Appender-question-tp23922806p23939439.html Sent from the Logback User mailing list archive at Nabble.com.
Problem solved Would be nice if the getAppenderTracker method is public. public class SiftingAppender extends SiftingAppenderBase<LoggingEvent> { public AppenderTracker<LoggingEvent> getAppenderTracker() { return appenderTracker; muleman wrote:
I built an appender that buffers messages and it will write the content to the appender on the stop method.
With this appender I want to collect messages that are related to a specific Object instance in my application. For example; I want to collect all messages that belong to one ProcessingRequest. Once this request is completed I want to flush it out to a Space as one string plus host and some more info....
I noticed that the appender does not exist any more after I call the stop method. Furthermore it looks like appenders are not created on a per logger basis, there seems to be just one appender instance ....
Is there a way to force a new appender instance for each logger ?
Thanks Chris
-- View this message in context: http://www.nabble.com/Appender-question-tp23922806p23939408.html Sent from the Logback User mailing list archive at Nabble.com.
participants (1)
-
muleman