Creating a Rule-Based Responsibility for Alerts 

Use

You can forward alerts to the Alert Management (ALM) to be informed about monitoring architecture alerts quickly and individually. Two auto-reaction methods are available for this:

●      CCMS_Send_Alert_to_ALM

You can use this method to forward alerts to the ALM. You can set the alert category as a parameter; you set the responsibility for the alert globally (irrespective of specific alert values) in Alert Management.

●      ccms_send_alert_to_alm_ccms_container_v4

You can also use this method to forward alerts to the ALM. The difference is that with this method, an alert category has already been set by default. This alert category allows you to use an assigned rule to set responsibilities for the alert depending on the alert data. The use of this method is described here.

Prerequisites

You have performed the necessary configuration steps for using Alert Management (see Alert Notification Step-by-Step).

Features

At the center of rule-based responsibility determination are responsibilities, which you can use to determine who is to be informed about an alert. The distribution of notifications is performed using values of the alert that are written to the rule contains of the CCMS rule.

Activities

If you want to define different responsibilities (for example, inform different administrators) for alerts of the CCMS monitoring infrastructure depending on alert data, proceed as follows:

...

       1.      Assign the auto-reaction method ccms_send_alert_to_alm_ccms_container_v4 to the desired node in the alert monitor (transaction RZ20). For detailed information: Configuring a Method to Forward Alerts to ALM.

This method forwards alerts for assigned nodes of the monitoring infrastructure to Alert Management (ALM). For this ALM alert:

○       The alert is assigned the alert category CCMS_CONT.

○       The alert container is filled with the values of the alert.

○       You can individually adjust the title, short text, and long text of the message that is sent in ALM based on the alert; when doing so, you can use the values of the alert container in these texts.

○       The alert category CCMS_CONT is assigned the rule CCMS(Responsibilities for CCMS Alerts); all alert values that could potentially be used to determine a responsibility are transferred to the rule container of this rule.

       2.      Start transaction ALRTCATDEF, select the alert classification CCMS ALERTS, and choose the alert category CCMS_CONT by double-clicking it. To ensure that the messages that are assigned to this alert category use the texts from the Short Text and Long Text tab page, choose the  Display/Change pushbutton, and deactivate the Dynamic Text indicator on the Properties tab page. Save your changes.

If the Dynamic Text indicator is activated, the title of the message is determined by parameters of the method ccms_send_alert_to_alm_ccms_container_v4.

       3.      Start transaction PFAC, and define the desired responsibilities there for the above rule CCMS on the tab page of the same name. Choose  (Create Responsibility).

       4.      In the Object Abbrev. field, enter CCMS; and in the Name field, enter an appropriate name for the responsibility. Choose  (Continue)

       5.      In the Responsibility Specs list, enter the values for the alerts with which you want to define the responsibility. A number of examples are presented below to explain how you can distribute the responsibilities for monitoring infrastructure alerts:

○       Responsibility by the ID of the system in which the alert occurred

You can divide the responsibility based on the system in which the alert occurs. To do this, in the Responsibility Specs list, enter the system ID of the desired monitored system in the System ID field.

Note that you cannot use this responsibility specification to determine the responsibility for alerts for availability monitoring with CCMSPING or GRMG, since these alerts technically always belong to the central monitoring system. The correct procedure is explained further below.

○       Responsibility by the instance in which the alert occurred

You can divide the responsibility based on the instance in which the alert occurs. To do this, enter SAP_CCMS_<instance name> in the Monitoring Segment field of the Responsibility Specs list. Use the usual naming convention for the instance name:

ABAP instance:     <Hostname>_<System ID>_<System Number>

Java instance: <Hostname>_<System ID>_<system number>_X

○       Responsibility by system availability (CCMSPING)

You can divide the responsibility based on the system for which an alert is reported in the context of the CCMSPING availability monitoring. These alerts are reported in a monitoring object. To do this, enter Availability: <System ID> on <host name> in the Monitoring Object field of the Responsibility Specs list, and replace <System ID> and <host name> with the desired values for the monitored system.

○       Responsibility by component availability (GRMG)

You can divide the responsibility based on the component for which an alert is reported in the context of the GRMG availability monitoring. These alerts are reported in a monitoring context. To do this, enter GRMG: <component><system ID> on <host name>in the Monitoring Context field of the Responsibility Specs list, and replace <component>, <System ID>, and <host name> with the desired values for the monitored component.

○       Responsibility by ID of system log alerts

For system log alerts, you can divide the responsibility based on the ID of the system log message. To do this, in the Responsibility Specs list, enter the three-character ID of the desired system log message in the External ID field.

○       Responsibility by MTE classes

You can divide the responsibility based on the MTE class in which the alert occurs. To do this, in the Responsibility Specs list, enter the name of the MTE class for the alerts of which you want to set the responsibility in the MTE Class field.

       6.      To be able to use a responsibility, ensure that you add a user assignment (more information: Assigning Users to a Responsibility).

       7.      Save your changes.

If an alert now occurs in one of the assigned nodes, the auto-reaction method is started and the responsible processor is informed based on the values of the alert.