Windows Event Tracing

[Keith Brown <ke...@pluralsight.com>]

I had my first look at log4net today, and it doesn't look like any of the
loggers write to the Windows Event Tracing service. I searched the list
archives for "Windows Event Tracing" and got zero hits.

Are there plans to have a logger over WET, or is there some architectural
reason why it's not under consideration?

Thanks!

Keith

Re: Windows Event Tracing

[Thibaut Barrère <th...@gmail.com>]

Thanks for the pointer!


On Wed, 29 Sep 2004 17:45:05 -0600, Keith Brown <ke...@pluralsight.com> wrote:
> >> Do you mean the application event log ?<<
> 
> Nope. Windows Event Tracing is a kernel-level feature that allows an
> application to spit out an incredible amount of log data (it's great for
> method tracing) in a short period of time, with minimal CPU impact (IIRC,
> the goal is around 5% additional CPU utilization with WET turned on).
> 
> Windows 2000/XP/2003 itself is instrumented using WET, and you can correlate
> kernel level logs with application level logs, e.g., how did the file system
> or Active Directory contribute to the time it took for my Tx to run, and
> exactly what was the file system or AD doing during that time?
> 
> Here's a link to an article describing WET:
> 
> http://www.winnetmag.com/Windows/Article/ArticleID/40707/40707.html
> 
> Microsoft's EIF supports logging to WET, but it sounds like EIF is being
> replaced by a new instrumentation platform, which explicitly says it does
> not support WET (why, I don't yet know). This is why I looked to log4net.
> Besides EIF, I know of no other mainstream managed WET support to recommend
> to clients.
> 
> Keith
> 
>

RE: Windows Event Tracing

[Keith Brown <ke...@pluralsight.com>]

>> Do you mean the application event log ?<<

Nope. Windows Event Tracing is a kernel-level feature that allows an
application to spit out an incredible amount of log data (it's great for
method tracing) in a short period of time, with minimal CPU impact (IIRC,
the goal is around 5% additional CPU utilization with WET turned on).

Windows 2000/XP/2003 itself is instrumented using WET, and you can correlate
kernel level logs with application level logs, e.g., how did the file system
or Active Directory contribute to the time it took for my Tx to run, and
exactly what was the file system or AD doing during that time?

Here's a link to an article describing WET:

http://www.winnetmag.com/Windows/Article/ArticleID/40707/40707.html

Microsoft's EIF supports logging to WET, but it sounds like EIF is being
replaced by a new instrumentation platform, which explicitly says it does
not support WET (why, I don't yet know). This is why I looked to log4net.
Besides EIF, I know of no other mainstream managed WET support to recommend
to clients.

Keith

Re: Windows Event Tracing

[Thibaut Barrère <th...@gmail.com>]

Hi Keith,

Do you mean the application event log ? There's an event log appender
which can do that :

http://logging.apache.org/log4net/release/config-examples.html#HC-11731442

regards

Thibaut


On Wed, 29 Sep 2004 14:34:45 -0600, Keith Brown <ke...@pluralsight.com> wrote:
> I had my first look at log4net today, and it doesn't look like any of the
> loggers write to the Windows Event Tracing service. I searched the list
> archives for "Windows Event Tracing" and got zero hits.
> 
> Are there plans to have a logger over WET, or is there some architectural
> reason why it's not under consideration?
> 
> Thanks!
> 
> Keith
> 
>