Agentless Exception Monitoring (AEM) application mapping management pack

Summary

This management pack contains elements specific to map generic errors sent by Windows Error Reporting (WER) clients to an AEM enabled Management Server. The mapping of known generic errors will provide more meaning full application view and application error group view with application names and versions.

Configuration

<Discovery ID="<Provide a unique ID>" Target="AEMLib!Microsoft.SystemCenter.CM.AEM.CrashListener" Enabled="true" ConfirmDelivery="true">

<Category>Discovery</Category>

<DiscoveryTypes>

<DiscoveryClass TypeID="AEMLib!Microsoft.SystemCenter.CM.AEM.MapperType" />

</DiscoveryTypes>

<DataSource ID="DS" TypeID="AEMLib!Microsoft.SystemCenter.CM.AEM.DiscoverMapperType">

<EventType>CLR20R3</EventType>

<ApplicationNameParameterNumber>2</ApplicationNameParameterNumber>

<ApplicationVersionParameterNumber>3</ApplicationVersionParameterNumber>

</DataSource>

</Discovery>

Additional

To create a new rule that will map a Generic Error Group Type you can use the sample configuration provided in the Configuration section. Modify the configuration above as follows:

• Provide a unique ID for the rule, example Microsoft.SystemCenter.ClientMonitoring.MyMP.CLR20R3Mapping

• In the EventType provide the event type you want to map. This is the generic error event type that you will see in the unknown error, usually Parameter1.

• Provide the parameter number from the EventType that maps to the application name that you want to see in the views. For example: CLR20R3 parameter number 2 is used to map to the application name.

• Provide the parameter number from the EventType that maps to the application version that you want to see in the views. For example: CLR20R3 parameter number 3 is used to map to the application version.

External

http://msdn2.microsoft.com/en-us/library/bb219076.aspx