Home

EventSourceProxy

EventSourceProxy (ESP) is the easiest way to add scalable Event Tracing for Windows (ETW) logging to your .NET program.

** Now in NuGet! **

Follow @jonwagnerdotcom for latest updates on this library or code.jonwagner.com for more detailed writeups.

Why You Want This

• You really should be logging more than you do now.
• ETW is the best way to log in Windows.
• It's about zero effort to add logging to new code.
• It's zero effort to add logging to existing interfaces.
• Generated IL keeps overhead low, and it's almost nothing if tracing is off.
• You have crazy interfaces, and want an easy way to log sane data. See Controlling Logged Data. It will blow your mind!

A Quick Tour

• A Quick Tour

Getting Started

• Getting Started
• About ETW
• About .NET EventSource
• Implementing an EventSource
• Implementing a Logging Interface
• How it Works

Some Tracing Basics

• Getting the EventSource Manifest or GUID
• To get the events into the Windows Event Log, see Getting the EventSource Manifest or GUID
• Using PerfView for ETW Tracing
• Using LogMan for ETW Tracing
• Using EntLib6 ETW Listeners

Managing the Details

• Controlling Logging Events through Attributes
• Controlling Logged Data
• Controlling Object Serialization
• Adding Additional Logging Context
• Managing Activity & Correlation IDs
• Overriding Event Implementation
• EventKeywords
• Logging Internal Classes

Tracing Existing Code

• Creating a Tracing Proxy for an Interface

Revision History

• Change Log

Other Stuff

• Want to get the data out of ETW? Use the Microsoft Enterprise Library Semantic Logging Application Block. It has ETW listeners to log to the console, rolling flat file, and databases, so you can integrate ETW with your existing log destinations.