Thanks. That might be useful.
I am in a process of programatically handling the stack trace to log it as a single message. But not sure syslog protocol/server has problem with line separator character which makes it display like this:

com.abc.main.init.InitializeMainAppJob.execute(InitializeMainAppJob.java:405)#015#012#011at org.quartz.core.JobRunShell.run(JobRunShell.java:202)#015#012#011at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)#015#012 com.abc.main.init.InitializeMainAppJ

any ideas?

Thanks,
Pradnya



2010/10/25 César Álvarez Núñez <cesar.alvarez.nunez@gmail.com>


On Fri, Oct 22, 2010 at 5:17 PM, Ceki Gulcu <ceki@qos.ch> wrote:
On 22.10.2010 17:02, Pradnya Gawade wrote:
Hi,

I have following requirements when sending the log from a java web
application to syslog server:


1. When logging the stack trace in case of exceptions, all the stack
strace should be seen as a single message.

Logback does not support this feature. Please create a jira issue asking for it.

Perhaps something like the indicated at "Useful Views"  may help you but using a http://logback.qos.ch/manual/layouts.html#customConversionSpecifier instead of a Log4J Layout.
HTH



2. Need to send either or all of the following information in logs- name
of the web application, URL, version of the application.

Via MDC
=======

Add the following code when your web-app starts:

MDC.put("appName", ...);
MDC.put("appURL", ...);
MDC.put("appVersion", ...);

In logback.xml:

<appender name="SYSLOG" class="ch.qos.logback.classic.net.SyslogAppender">
  <SuffixPattern>%mdc{appName} %mdc{appURL} %mdc{appVersion} %logger
%msg</SuffixPattern>
</appender>


By system properties
====================

Set the following system properties:

-DappName=... -DappURL=... -DappVersion

In logback.xml:

<appender name="SYSLOG"
class="ch.qos.logback.classic.net.SyslogAppender">
  <SuffixPattern>%property{appName} %property{appURL}
%property{appVersion} %logger  %msg</SuffixPattern>
</appender>

HTH


As per my knowledge, Syslog appender of Logback doesnot fit to above
requirements. I am also looking for any other logging APIs which can
satisfy these requirements. Any ideas? Thanks in advance.

- Pradnya



_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
http://qos.ch/mailman/listinfo/logback-user


_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
http://qos.ch/mailman/listinfo/logback-user