[logback-user] parameter { } substitution is not happening with our custom appender

Bob DeRemer bob.deremer at burningskysoftware.com
Wed Sep 22 12:37:11 CEST 2010

Your wild guess was right, thanks!


From: logback-user-bounces at qos.ch [mailto:logback-user-bounces at qos.ch] On
Behalf Of Joern Huxhorn
Sent: Tuesday, September 21, 2010 5:27 PM
To: logback users list
Subject: Re: [logback-user] parameter { } substitution is not happening with
our custom appender


Hi Bob,


I'm making a wild guess:

Is it possible that your custom appender is using loggingEvent.getMessage()
instead of loggingEvent.getFormattedMessage()?





On 21.09.2010, at 15:39, Bob DeRemer wrote:

Hi Logback community,


We created a custom appender to send logging data to our own storage medium.
It extends AppenderBase<ILoggingEvent> like the docs say, but for some
reason, any logging statements where we use the logback parameter
substitution (i.e. "message with parameter {}", param1), there is no
substitution.  We have our custom appender AND a FileAppender.  The
fileappender has the parameter substituted, but the custom one does not. 


If anyone has any suggestions, I would greatly appreciate.




Bob DeRemer

Senior Director, Architecture and Development


http://www.burningskysoftware.com <http://www.burningskysoftware.com/> 

O: 717.505.7923

M: 717.881.3986


Logback-user mailing list
Logback-user at qos.ch


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://qos.ch/pipermail/logback-user/attachments/20100922/860669d1/attachment-0001.html>

More information about the Logback-user mailing list