[This is preliminary documentation and subject to change.]
The Windows NT Event Log Provider functions as both an instance provider and an event provider. As an instance provider, the Event Log Provider returns data that describes events that have been logged to the Windows NT Event Log service and stored as formatted records in a log file. Typically, three log files reside on every machine: application, system, and security; Windows NT 5.0 has a fourth for directory events. The format for events is defined in the Win32 EVENTLOGRECORD data structure. The Event Log Provider maps each field in the EVENTLOGRECORD to a property in an instance of the Win32_NTLogEvent class. The Event Log Provider supports the Win32_NTLogEvent class for describing Windows NT events.
he Event Log instance Provider exposes an implementation of the IWbemProviderInit interface for initialization and implementations of the following methods of the IWbemServices interface:
Clients of the Event Log Provider can call either the asychronous or synchronous version of these methods. However, because all WBEM providers only implement the asynchronous IWbemServices methods, it is up to CIMOM to pass all client requests asynchronously.
As an event provider, the Event Log Provider registers with the NT Event Log service to receive notifications of new NT events. For each notification that it receives, the Event Log Provider generates a corresponding WBEM event by creating an instance of the __InstanceCreationEvent class. The Event Log Provider embeds an instance of Win32_NTLogEvent class as the TargetInstance property with the data taken from the logged event. CIMOM sends the instance creation event to all consumers that have registered to receive events of type __InstanceCreationEvent with an embedded Win32_NTLogEvent.
The Win32_EventlogFile and Win32_NTLogEvent classes and related association classes are included as part of the Win32 schema. The Event Log Provider is supported only in the \Root\Cimv2 namespace.