<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7601.18269"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=913142709-18102013><FONT color=#0000ff
size=2 face=Arial>FWIW, I tend to use SMTPAppender to show more
context.</FONT></SPAN></DIV><BR>
<DIV dir=ltr lang=de class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> logback-dev
[mailto:logback-dev-bounces@qos.ch] <B>On Behalf Of </B>Roman
Ivanov<BR><B>Sent:</B> Friday, October 18, 2013 2:15 AM<BR><B>To:</B>
logback-dev@qos.ch<BR><B>Subject:</B> [logback-dev] exceptionMessageIncluded
parameter for SyslogAppender<BR></FONT><BR></DIV>
<DIV></DIV>Hi Developers,<BR><BR>Does it make sense to extend SysLogAppender
with <SPAN
style="TEXT-ALIGN: left; TEXT-TRANSFORM: none; BACKGROUND-COLOR: rgb(192,161,84); TEXT-INDENT: 0px; DISPLAY: inline !important; FONT: 14px/20px Arial, Tahoma, Helvetica, FreeSans, sans-serif; WHITE-SPACE: normal; FLOAT: none; LETTER-SPACING: normal; COLOR: rgb(51,51,51); WORD-SPACING: 0px; -webkit-text-stroke-width: 0px"
data-mce-style="color: #333333;font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif;font-size: 14px;font-style: normal;font-variant: normal;font-weight: normal;letter-spacing: normal;line-height: 20px;orphans: auto;text-align: left;text-indent: 0px;text-transform: none;white-space: normal;widows: auto;word-spacing: 0px;-webkit-text-stroke-width: 0px;background-color: #c0a154;display: inline !important;float: none;"></SPAN>"throwableMessageAppended"
field to allow attach Exception/Throwable message<BR>to event ?<BR><BR>Reason:
Syslog is non linux/unix event logging system that does not support multi-line,
so java developers play with substitution of EndOfLine symbols to make it
conform unix rules for event logging. But in this case event become unreadable
if full stacktrace is in event. It is most likely required only to see Exception
message and then decide how to react on problem.<BR><BR>No message nor full
stacktrace is enough to investigate and fix problem - developer need see full
log from job and context of event before. So having ability to have in Syslog
only exception message is more convenient and short.<BR><BR>In detail, and
examples: <A
href="http://roman-ivanov.blogspot.com/2013/10/logging-exception-message-in-log-event.html"
target=_blank
data-mce-href="http://roman-ivanov.blogspot.com/2013/10/logging-exception-message-in-log-event.html">http://roman-ivanov.blogspot.com/2013/10/logging-exception-message-in-log-event.html</A><BR><BR>Thanks,<BR>Roman
Ivanov<BR></BODY></HTML>