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:
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.
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.
You have performed the necessary configuration steps for using Alert Management.
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.
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:
This method forwards alerts for assigned nodes of the monitoring infrastructure to Alert Management (ALM). For this ALM alert:
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.
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.
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 Specslist. Use the usual naming convention for the instance name:
ABAP instance: <host name>_<system ID>_<system number>
Java instance: <host name>_<system ID>_<system number>_X
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.
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.
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.
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.
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.