Bind alerts to a process CI

The association between an application process and a CI type is helpful for alert remediation. The association allows an event rule transform to generate an alert and bind the correct CI type. A CI type can map to more than one business process. For example, the cmdb_ci_apache_web_server CI type can bind to http.* and apache.* business processes.

Before you begin

Role required: evt_mgmt_admin or evt_mgmt_operator

About this task

You can define a pattern of processes that matches with the sa_process_name variable. The sa_process_name variable must be filled with the process name using an event rule. The Process to CI Type Mapping table is used for process binding. The table includes default patterns. The pattern variables extract from this table according to the host related CI Type. The table contains these columns for process binding:
  • The Process field contains the process pattern. Use any combination of free text, regex, and pattern.
  • The ci_type field contains the CI type in CMDB.

Binding an alert to a process, Event Management first receives all the processes that are running on the node (the alert resolving node). Then, Event Management matches every related process pattern with the name that is defined in the sa_process_name variable. Regular expressions are supported.

For example, if the sa_process_name contains /ora92/pmon_U2P3_db for an Oracle instance:
  • The sa_process_name variable must be filled by the event rule to store the process name.
  • The Process to CI Type Mapping table has the following record: 
Process: ${oracle_home}/pmon_${instance}
CI type: cmdb_ci_db_ora_instance.
  • Binding the process, Event Management finds a process of type cmdb_ci_db_ora_instance is running on the node.
  • Event Management matches /ora92/pmon_U2P3_db from the sa_process_name variable with the process pattern from the Process to CI Type Mapping table for type cmdb_ci_db_ora_instance.
  • If the Oracle instance has ${oracle_home} = ora92 and ${instance} = U2P3_db extracted from the database, then there is a match and this Oracle process is bound in the alert cmdb_ci. 
/ora92/pmon_U2P3_db= ${oracle_home}/pmon_${instance}.
You can assign custom-developed business process applications to CI types. The following default CI Types automatically bind to application process names during alert generation. The CI Types have global domain availability. The Process to CI Type Mapping [em_binding_process_map] table stores the mappings for the binding process.
Table 1. Default mappings
Default CI Type Application Process Name
cmdb_ci_apache_web_server httpd.*, apache.*
cmdb_ci_appl_ibm_wmq runmqlsr.*
cmdb_ci_app_server_jboss org.jboss.*
cmdb_ci_app_server_tomcat tomcat.*
cmdb_ci_app_server_weblogic weblogic.Server, beasvc.exe
cmdb_ci_db_db2_instance db2sysc.*
cmdb_ci_db_mssql_server sqlServer.exe
cmdb_ci_db_mysql_instance mysqld.*
cmdb_ci_db_ora_instance pmon_${instance}, *tnslsnr.*
cmdb_ci_endpoint_iis w3wp.exe
cmdb_ci_nginx_web_server nginx.*


  1. Navigate to Event Management > Settings > Process to CI Type Mapping.
  2. Click New or double-click a CI type.
  3. Type the process Name, and then select a CI type.
  4. Click Submit.