Noel - thank you for the guidance. Not to belabor the point, but Entlib 5.0 does allow me to configure Logging Application Block to send to WMI through Fluent API (see code below) and when I step through code, even for non-trace events, I do see a WMI event
getting fired from inside code (In Microsoft.Practices.EnterpriseLibrary.Logging.TraceListeners.WmiTraceListener.Write(), there is a call to ManagementInstrumentation.Fire(logEntry)).
Here is the Fluent API LAB setup:
Here is the Code from Microsoft.Practices.EnterpriseLibrary.Logging.TraceListeners.WmiTraceListener.Write()
var builder = new ConfigurationSourceBuilder();
.SendTo.Wmi("WMI Trace Listener");
public override void Write(string message)
LogEntry logEntry = new LogEntry();
logEntry.Message = message;
Evidently, dropping support for non-trace WMI events didn't lead to shutdown of code paths; it would get done in some future release?
For trace events, would you know what it would show up on the WMI side as? How do I trap a WMI trace event that originated in Entlib, on the WMI side? Would you have a WQL query for it?