Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts SAM Adapters: How to configure alertmapper.conf for Smarts SAM Microsoft Operations Manager 2007 Adapter (323570)

Last Updated: 12/17/2018Categories: How toTotal Views: 2047Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

This article explains how to configure Microsoft Operations Manager 2007 Adapter alertmapper.conf configuration file, located at : <SAMAdapters>\smarts\conf\OpsMgr2007\event\AlertMapper.conf

The settings in the alertmapper.conf configuration file determine how events coming from Microsoft OpsMgr are mapped into the Smarts SAM console.

There are four sections/types of entries in the alertmapper.conf file.

Default: Identifies the notification fields. This section allows you to define the values for the fields. Values defined here can and may be overwritten by the either the eventMgr.asl file or by the hook script file.

Template: Defines a single template. A template is used to configure fields that are used in multiple places in the file. A template can extend another template allowing for hierarchies.

Rules: Defines the rules that are used to configure the notification fields. The rules define the conditions that are used to identify the type of notification, define which template to be used, and any additional parameters to be configured.

Finally: Specifies which template to use and which fields to configure when no template satisfies any of the rules defined in the Rules section.

The following presents the considerations and examples for configuring entries in the different sections of the alertmapper.conf file.

Default section
Customers should set the default section to set variables and mappings that are common for most of the events.  These may be overridden by subsequent templates or rules.

Template section
A template entry can either inherit directly from the default settings, or inherit from another template. Let's examine the following example:

Template GenericTemplate
{
UserDefined1 = "This is the base template"
UserDefined2 = "This is the base template sub-definition"
}

Template SoftwareService extends GenericTemplate
{
UserDefined1 = "This is a software Service"
}

Template HardwareRouter extends GenericTemplate
{
UserDefined1 = "This is a hardware router"
UserDefined2 = "This is hardware router sub-definition"
}

Note the following about the above example:

If a rule uses the GenericTemplate, the UserDefined1 would be set to "This is the base template" and UserDefined2 would be set to  This is the base template sub-definition"

If a rule uses the SoftwareService template, UserDefined1 would be set to "This is a software Service" and UserDefined2 would still be set to  This is the base template sub-definition"

A rule using the HardwareRouter template would cause UserDefined1 to be set to "This is a hardware router" and UserDefined2 would be set to  This is hardware router sub-definition".

Rules section
The Rules section is where Operations Manager events are mapped to Smarts SAM notifications. The system will process the rules in the order in which they are present in the alertmapper.conf file. Once a rule is matched, no further rules are processed. Therefore, the rules should go from most specific to least specific. The following is an example of a rules section:

Rules
{
Test E_ClassName == 'Microsoft.Windows.InternetInformationServices.2003.WebSite'
Use DefaultOpsMgrTemplate
ClassName               = "SoftwareService"
ClassDisplayName        = ClassName
EventName               = E_EventName
CreateClassName         = "Host"
CreateClassInstance     = ComputerName

Test E_ClassName == 'Microsoft.Windows.Computer'
Use HostPerformanceTemplate

Test E_ClassName =* 'Microsoft.*'
Use DefaultOpsMgrTemplate

Test E_ClassName =* 'TCPPortCheck_*Group'
V_CreateNotification    = "FALSE"

Test E_ClassName =* 'TCPPortCheck_*'
Use DefaultOpsMgrTemplate
ClassName               = "SoftwareService"
ClassDisplayName        = ClassName
EventName               = "${E_EventName}-${E_InstanceName}"
CreateClassName         = "Host"
CreateClassInstance     = ComputerName

}

In the above example, note the following:

Events coming from Operations Manager concerning the IIS 2003 Webserver would use the DefaultOpsMgrTemplate, set ClassName to "SoftwareService", and so on.

Events with the ClassName "Microsoft.Windows.Computer" would use the HostPerformanceTemplate.

Any other Microsoft events would just use the DefaultOpsMgrTemplate

Events which have a TCPPortCheck Group class name would not have an Ionix notification created as the V_CreateNotification is set to "FALSE"

Any other TCPPortCheck events would use the DefaultOpsMgrTemplate, and so on.

Finally section
There is only one entry in the "Finally" section.  This is the action to be taken if the event did not match any of the specified rules. Common options here are to use the generic template, or more often set the V_CreateNotification to FALSE.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant