SAP Library - Find your answers

You can use the monitoring architecture to monitor selected jobs and to display problems as alerts (see Monitoring Jobs with the Alert Monitor). This job monitoring is deactivated by default; activation is described in Activating Monitoring of Jobs with the Alert Monitor.

After activation, the data is available in the context Background, Background Job Monitoring subtree. For the monitoring, it is useful to define your own monitor or to extend a monitor definition of your own to display the data. The monitor definition and the monitor produced from it are described here.

Prerequisites

You can define a rule-based or a static monitor to display data. For basic information about this, see Creating and Changing Monitors. For a rule-based monitor, the definition must contain a rule CCMS_GET_MTE_BY_CLASS with Job_Monitoring as the MTE class:

If you are using a static monitor, choose the context Background ® Background Job Monitoring for the desired system:

Features

With the definition above, the monitor created has the following structure. Here, the job SCHEDULED_JOB1 and all jobs whose names begin with JOB_EXAMPLE are to be monitored. A subtree is created for every name pattern for a monitored job (job chain):

The monitor contains the following monitoring tree elements (MTEs):

Customizing Alert Generation

· Runtime, Delay and Delay + Runtime

Threshold values are already assigned to these performance attributes by default, so that an alert is generated as of a defined runtime or delay. To change the threshold value, select the desired performance attribute and choose Properties (see Changing Properties and Method Assignments). Ensure that you choose Edit ® Properties ® Use for individual MTE so that you do not change the threshold values for the other monitored jobs.

· History and Log of Current Job

By default, these log attributes always have the color green. However, you can also assign a yellow or red alert to particular messages of the attribute. To do this, choose Properties and specify the class and ID of the desired message on the Filter tab page.

To determine this data for a message of the log attribute, follow the procedure below:

i. Select the desired log attribute and choose the Display Details button ().

ii. The Monitoring Attributes - Detail Data screen appears. To do this, select any row from the list of messages and choose Current Display Variant ().

iii. The Change Layout screen appears. Ensure that the fields for message class (MsgKlasse) and the message ID (MsgId) are displayed, and accept the changes.

iv. The class and ID of the message are now displayed in the list.

The enqueue service allows ABAP applications to lock data so that only they can use it. The locking of the data avoids parallel changes to the data, which would lead to data inconsistency. For more information, see The SAP Lock Concept (BC-CST-EQ).

There are two different trees in the monitoring infrastructure for monitoring the enqueue service:

· Enqueue monitor in the SAP CCMS Monitor Templates monitor set

This monitor includes a large number (see below) of monitoring values for the enqueue service. Since the monitor is supplied with values by an ABAP data collection method, the values are updated every five minutes.

· Enqueue subtree in the R3Services subtree of the Entire System Monitor (SAP CCMS Monitor Templates monitor set)

This subtree includes only the most important monitoring values for the enqueue service. Since the data is supplied by an active data supplier directly from the kernel, current data is reported immediately in the monitoring infrastructure.

Enqueue Monitor

Features

The monitor contains the following monitoring tree elements (MTEs):

Activities

To start the monitor, follow the procedure below:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Enqueue Server monitor from the list by double-clicking it.

Enqueue Subtree in R3Services

Features

The subtree contains the following MTEs:

Activities

To display the subtree, proceed as follows:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Entire System monitor from the list by double-clicking it, and expand the monitoring tree along the path ® ApplicationServer ® ® R3Services ® Enqueue.

The monitoring tree is the component hierarchy displayed by the Alert Monitor. If problems occur in your system, they are displayed as alerts in the monitoring tree. The system displays a schematic representation of the monitoring tree:

To give a better overview, alerts are assigned certain colors - yellow for a warning and red for a problem - and a numerical value for the severity of the error. The alert with the highest severity appears at the top of the monitor that displays the monitored IT components (such as the CPU of a server) including their attributes (such as CPU usage) in a tree structure. In accordance with this, a node of the tree structure displays the most severe alert of the whole branch below it. If a node is not displaying an alert, there is no error in the whole branch below it. The system administrator can choose between different Views of the Alert Monitor, and display the current or open (that is, those that have not been analyzed) problem messages.

See Also:

The Monitoring Architecture: Concept

Actions in the Alert Monitoring Tree

Components of the Alert Monitor

The alert monitoring tree provides you with an overview of the system status of monitored systems. There are various options for displaying and checking the alerts that have occurred. The most important commands that you can use in the alert monitoring tree are described here.

Activities

• Choose Expand Tree () or the folder icon () directly in front of the relevant branch in the Alert Monitor to expand the individual branches of the alert monitoring tree.
• Choose Compress Tree () or the folder icon () directly in front of the relevant branch in the Alert Monitor to compress the individual branches of the alert monitoring tree.
• Select an element in the monitoring tree and choose
F1 to display a description of the element.
• If the central data cache is active in the display of the alert monitoring tree (this sentence is then displayed at the top of the monitoring tree), you can delete the entries of the central data cache and regenerate the monitor. To do this, choose Refresh and Invalidate Data Cache ().

• In the Current Status display, choose an element by double clicking it to start the analysis method assigned to this element. You can use this to analyze and complete any alerts that exist (see
Starting Methods).
• In the Open Alerts display, choose an element by double clicking it to start the
Alert Browser. This displays all alerts that have not yet been analyzed.
• Choose Display Details () to display the detail data for this element. This includes, above all, the values reported for this element during the last 24 hours (see
Display Detail Data and Tailor Display).
• Choose Properties to display the
Properties and Methods assigned to the element. These include, above all, the threshold values for warnings and problems (yellow and red alerts) and the associated analysis and auto-reaction methods.
• Choose Extras ® Activate Maintenance Function to be able to make changes to monitors. The Change Monitor pushbutton () then appears in addition on the toolbar.
• To switch between different monitors or monitor sets, choose Previous Monitor () and Next Monitor ().

See also:

Selecting Nodes in the Alert Monitoring Tree

Use

In the configuration of availability monitoring with CCMSPING, you can deactivate the monitoring during certain specified times, such as during the weekend or for maintenance work. You can also repeat these monitoring pauses daily or weekly.

Prerequisites

This procedure is part of the Configuring Availability Monitoring process. It is therefore a prerequisite that you have already performed the part of the process that is to be performed before this procedure.

Procedure

The system is displaying the Configure Availability and Performance Overview screen. If you want to create or change a monitoring pause for monitored systems, follow the procedure below:

...

...

1. Select the desired systems by choosing the folder symbol for the corresponding systems.

Note that a system is only correctly selected when the entire line is highlighted:

2. If you have only selected one system, or want to create different monitoring pauses for the selected systems, choose the Pauses button and then Create Monitoring Pause.

If you want to create an identical monitoring pause for the selected systems, choose the Pauses button and then Create Uniform Monitoring Pause.

3. The Maintain Time not Monitored screen appears. The screen has the following structure:

4. You can define monitoring rules for single monitoring pauses, and pauses that are repeated daily or weekly. The monitoring pauses that are repeated daily take effect immediately, the monitoring pauses that are repeated weekly are valid from the time specified, each time for the selected period of time and on the selected weekday.

5. Save the monitoring rule that you have created. Once you have successfully saved your rule, the system displays a success message and your rule appears in the list at the bottom of the screen. If you have selected multiple systems, and do not want to create a uniform monitoring pause, repeat these steps for all selected systems.

To change a monitoring rule, delete the rule from the list, and recreate the rule.

6. To leave the screen, choose Cancel ()

Result

The selected systems are not monitored for their availability during the specified times; that is, no corresponding alerts are generated during these time periods.

Availability Monitoring with CCMSPING start page

Monitoring objects and attributes are assigned various properties. These include:

· An explanatory text

· When and under which conditions Alerts are generated

· The criticality that an alert is assigned

· The maximum number of alerts that are to be stored for an attribute

The properties therefore provide settings options for the alert that can be assigned to a monitoring attribute, and also more detailed information through the assigned message. In the same way as the properties, methods are assigned to a monitoring attribute.

The properties for most monitoring objects and attributes in the monitoring architecture are already predefined and are available in every SAP system. However, you can also change the settings in accordance with your wishes. Your changes to the properties and methods are grouped in properties variants, which prevents an accidental reset of your adjustments when the SAP predefined settings are updated (for example, during an update).

Structure

The properties are divided into two groups:

· General Properties

This includes the assigned message that contains more detailed information about the monitoring object or attribute. As the properties contain the class and the number of the message, you can also make your own changes here.

Setting options for the alerts are also general properties. For a monitoring object, these properties are only valid for the attributes that belong to this object.

· Properties of the Individual Monitoring Attributes

There are five different attribute types in the monitoring architecture, each of which have their own special properties. In this way, you can, for example, define the threshold value only for performance attributes. These properties only exist for monitoring attributes, not for monitoring objects.

See also:

Properties of Log Attributes

Properties of Performance Attributes

Properties of Status Attributes

You can edit properties both from the alert monitoring tree and from the Customizing transaction RZ21 (see Changing Properties and Method Assignments).

Definition

A monitoring object represents a component of the IT environment that is to be monitored, such as the CPU of a server, the dialog system, or background processing. Monitoring attributes are values, statuses, or texts that are reported to this object, such as the CPU utilization, or the average response time in the dialog system. A monitoring attribute can be assigned an alert. The selection of the monitoring objects is performed using the data suppliers that exist for all areas of system management.

Structure

Monitoring objects and their attributes are displayed in the alert monitoring tree as individual nodes in a hierarchical tree. If the data reported to the monitoring architecture exceeds or falls below the defined alert threshold values, an alert is triggered in the corresponding monitoring tree element.

There are five different types of monitoring attributes:

You can assign methods to monitoring attributes. A method can be a report, a function module, an SAP transaction, or a URL that is to executed as a reaction to an alert. You can execute these methods within the Alert Monitor. If you double click, for example, the MTE for prematurely terminated jobs, the monitoring architecture automatically starts the job management transaction, in which the job reported in the MTE is already selected.

See also:

Properties of Log Attributes

Properties of Performance Attributes

Properties of Status Attributes