Integrate > VMware vRealize Operations Manager > Configure > Entity Mappings > Mappings Used in Event Integration

Mappings Used in Event Integration

OpsCx for VROPS includes preconfigured event mappings and rules that you can customize. The mappings and rules are defined in the Operations Connector policy for VROPS events. To reconfigure them, make sure the policy is imported into Operations Connector, and then edit it in the Operations Connector web interface.

Default Event Mappings and Rules

Default Severity Level Mapping

 
VROPS Alert Criticality OMi Event Severity

CRITICAL

Critical

IMMEDIATE

Major
WARNING Warning
INFO Normal
NONE Unknown

Default Event Attributes

 

Event Policy Attribute VROPS Alert Attribute(s) Mapping

Title

info  

Description

info

source_name
 
Severity alertlevel <$MAP(mapalertlevel)>
Time Created starttimeutc  

Category

VROps *  
Node source_name  
Related CI source_mame  
Source CI drilldown_location  
Source Event ID VROps:alertID  
Send with closed status true or false based on statusid <$MAP(mapStatus)>

* This is a literal value

Policy Rules

Rule Event Type Indicator Mapping
HostNotResponding

PingAvailability:Available or PingAvailability:Unavailable

<$MAP(mapETIVal-ResAvail|Unavail)>
ResourceDown NodeStatus:Up or NodeStatus:Down <$MAP(mapETIVal-ResUpDown)>

The entire event type indicator (ETI) mapping is based on the alertlevel event attribute in VROPS. An alert level value should be mapped to the correct ETI value.

Rules not listed in the previous table do not set an ETI. They only attempt to relate the event to the corresponding configuration item (CI) in the Run-Time Service Model (RTSM) database of OMi.