This project has moved and is read-only. For the latest updates, please go here.

Can Essential Diganostics help create a hierarchy of lognames in the windows event system?

Sep 3, 2012 at 12:46 PM

With reference to the question posed here:

Best regards,
Ronny Hanssen

Nov 11, 2012 at 4:47 AM
Edited Nov 11, 2012 at 4:47 AM

Is there a listener in the DLL that writes a hierarchy of log names?  Not that I am aware of. Maybe some of the newer event logging for windows (ETW) -- not sure.

Can Essential.Diagnostics help? I suppose so. It would be a good feature for an enhanced version of EventLogTraceListener, so add it to the issue tracker as a feature request. Start from TraceListenerBase is also a good way to create new listeners (do it as a fork, push back to CodePlex, then send me a pull request).

However -- should you do it? The original SO questions talks about pushing both warning/criticals destined for the Windows Event Log through EntLib (presumably as well as logging/tracing code) and then relying on configuration to direct them correctly.

As discussed in the trace levels guidance in this project (, I generally send warnings/criticals directly to the Windows Event Log, i.e. without a way to turn it on/off or change configuration. (I would also duplicate/include the same messages in the trace output, but would normally assume there is not a trace listener attached).

If you are sending it directly then the trace framework you are using isn't involved.