There are various different ways to arrange this sort of logging
depending if you only want the INFO message from a single class (or
logger subtree). 
One way to achieve the result is using the threshold:


    <log4net>
        <appender name="smtpAppender"
type="log4net.Appender.HtmlSmtpAppender">
            <threshold value="ERROR" />
            <to value=" [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> " />
            <from value="[EMAIL PROTECTED]" />
            <subject value="Application Error" />
            <smtpHost value="somesmtpserver.com" />
        </appender>
        <appender name="rollingFileAppender"
type="log4net.Appender.RollingFileAppender " >
            <file value="Application.log" />
            <RollingStyle value="Date" />
            <datePattern value="yyyyMMdd" />
            <layout type=" log4net.Layout.PatternLayout">
                <conversionPattern value="%newline%date %-4timestamp
[%thread] %-5level %logger %ndc - %message%newline" />
            </layout>
        </appender> 
        
        <!-- Set root logger level to DEBUG and its only appender to A1
-->
        <root>
            <level value="ERROR" />
            <appender-ref ref="smtpAppender" /> 
            <appender-ref ref="rollingFileAppender" />
        </root>
        <logger name="MyNamespace.MyClass">
            <level value="INFO" />
        </logger> 
    </log4net> 


The <threshold value="ERROR" /> on the smtpAppender limits the events
that are sent via the appender to only ERROR and above. The 2 appenders
are attached to the <root> logger, this means that all errors will also
be logged to the rollingFileAppender as well as the smtpAppender.

Cheers,
Nicko

> -----Original Message-----
> From: Mike Raath [mailto:[EMAIL PROTECTED] 
> Sent: 21 December 2005 09:04
> To: [email protected]
> Subject: BUG? Parent appenders log based on child appender level
> 
> I've got a requirement where I need one appender to log info 
> level messages to a log file, which I've defined as a 
> RollingFileAppender, and error messages to a mail, which is 
> an appender I've written myself called HtmlSmtpAppender (see 
> my earlier post regarding html format mails). 
> 
> The config entry looks like this:
> 
>     <log4net>
>         <appender name="smtpAppender" 
> type="log4net.Appender.HtmlSmtpAppender">
>             <to value=" [EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]> " />
>             <from value="[EMAIL PROTECTED]" />
>             <subject value="Application Error" />
>             <smtpHost value="somesmtpserver.com" />
>         </appender>
>         <appender name="rollingFileAppender" 
> type="log4net.Appender.RollingFileAppender " >
>             <file value="Application.log" />
>             <RollingStyle value="Date" />
>             <datePattern value="yyyyMMdd" />
>             <layout type=" log4net.Layout.PatternLayout">
>                 <conversionPattern value="%newline%date 
> %-4timestamp [%thread] %-5level %logger %ndc - %message%newline" />
>             </layout>
>         </appender> 
>         
>         <!-- Set root logger level to DEBUG and its only 
> appender to A1 -->
>         <root>
>             <level value="ERROR" />
>             <appender-ref ref="smtpAppender" /> 
>         </root>
>         <logger name="MyNamespace.MyClass">
>             <level value="INFO" />
>             <appender-ref ref="rollingFileAppender" />
>         </logger> 
>     </log4net>
> 
> 
> 
> Now what I've noticed is that when an INFO event is logged, 
> the MyNameSpace.MyClass Logger is tested against the defined 
> log level and correctly called. However, when the appender 
> hierarchy is iterated, and we get to the root logger, its 
> append is called even though it has a level set to error. 
> 
> Is this an error in my understanding of how the hierarchy is 
> used, or is it a bug? I wanted a catch-all error logger but 
> obviously I can achieve what I want as things currently stand 
> by defining a root debug logger and a class (or parent 
> namespce) logger which logs error events. 
> 
> Regards,
> Mike
> 
> 

Reply via email to