Friday, May 18, 2012
 
The best way to analyze your logs! Minimize
 Log4Net Mail archive   

The Log4Net mailing list is a great source of information about using log4Net, in this forum we collect all the messages in the log4net user list and some selected threads from the developer list.

Subject: Excluding stack trace from Layout
Prev Next
You are not authorized to post a reply.

Author Messages
Hsalim

07/30/2008 4:11 PM  

Hi,

I have tried to search for an answer here and tried to understand the
documentation but can't say I have been successful.

I'm using this configuration value for the layout pattern:

<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%date %newline [%thread] %newline %-5level :
%message %newline" />
</layout>

This is too much information.  I don't want the stack trace, only
exception.messge and exception.InnerException.

How do I specify that in the layout?

Thanks in advance for helping.

Habib
--
View this message in context: http://www.nabble.com/Excluding-stack-trace-from-Layout-tp18734170p18734170.html
Sent from the Log4net - Users mailing list archive at Nabble.com.

Yann Luppo

07/30/2008 5:47 PM  

I believe the place holder "%message" refers to the data sent when you do log.Debug(message). I think it's more about how you build the message in the logger that matter in your case. Try to send us your logger call maybe.

Yann

Hsalim

07/30/2008 6:55 PM  

Yann,
Thanks for the reply.
I guess I could do

catch (Exception ex)
{
if (log.IsWarnEnabled)
 log.Warn(string.Format("Error blah {0}:{1}\n{2}\n{3}", key1, key2,
ex.Message, ex.InnerException));
}

Instead, I would prefer to pass in the exception
log.Warn(string.Format("error blah {0}:{1}", key1,key2 ), ex);

I want to use an exception layout to selectively log parts of the exception.
I'll use a text file appender to log the stack trace and every gory detail
and use an SMTP appender to semd me just the exception message and
InnerException.  And I can change what gets logged at any time.

I see from the SDK that there is an exception layout but I just cant figure
out what I need to do.

regards
Habib

--
View this message in context: http://www.nabble.com/Excluding-stack-trace-from-Layout-tp18734170p18737810.html
Sent from the Log4net - Users mailing list archive at Nabble.com.

Freddy Gómez

07/31/2008 1:42 AM  
Although you solved you problem by parsing the exception I'll give you an alternative to do such a job.

You can implement a Renderer (a class which implements the interface IObjectRenderer) for your exception and put the information you want about the exception. Then, you just have to add a <renderer renderingClass="MyClass.MyRenderer" renderedClass="Exception" /> element to the config file.

regards,

Fred
Hsalim

07/31/2008 7:22 AM  


Thanks.  I am still too new to this world and still mulling my way through.

--
View this message in context: http://www.nabble.com/Excluding-stack-trace-from-Layout-tp18734170p18747950.html
Sent from the Log4net - Users mailing list archive at Nabble.com.

You are not authorized to post a reply.
Forums > Log4Net > Log4Net Mail archive > Excluding stack trace from Layout



ActiveForums 3.7

 

 

 

 

 

 

 

 

Log4Net Dashboard

Log analysis and monitoring made easy!

Log4Net Dashboard is a log viewer that can read log statements from a variety of logging output targets.

You can download a free developer version.

  

Check it out!

On the demonstration site you can try it  with live data.demo.l4ndash.com - Try Log4Net Dashboard with live data

The mail archive is a copy of all the mail sent to the mail address: log4net-user@logging.apache.org, organized as a forum.

If you would like to participate in the mail list, send a mail to log4net-user-subscribe@logging.apache.org.

More information about the mailing list is available on: http://logging.apache.org/log4net/support.html

 

A complete topic list is available and can be viewed here (warning, it takes some time to load)

 

Copyright 2005-2008 by FaktNet AS Terms Of Use Privacy Statement