You can only access many functions for monitoring tree elements (MTEs) in the alert monitoring tree once you have selected the relevant MTEs. This is simplest for individual MTEs, which you can select by selecting the indicator in front of the MTE. There are also various commands with which you can quickly select a larger number of MTEs.

Selecting MTEs in the Tree

Deleting Selection of MTEs in the Tree

Display Overview of All Selected MTEs in the Monitoring Tree

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.
2. Expand the monitor set that contains the monitors that you require and choose Start Monitor.
3. Select the desired MTEs.
4. Choose Edit
® Selections ® Show selections.

Set Selection Behavior

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.
2. Expand the monitor set that contains the monitors that you require and choose Start Monitor.
3. Select Edit
® Selections ® Selection Behavior.
4. In the Selections by Operation group box select one of the radio buttons Hold or Delete. By doing so, you decide whether the selection is retained after an operation (such as Display Details).

See Also:

Actions in the Alert Monitoring Tree

Definition

A monitor is a set of monitoring tree elements (MTEs) that are arranged in a hierarchical structure (the Alert Monitoring Tree). As monitors are organized by topic, you can quickly check all of the important objects for this topic. Monitors are combined in monitor sets.

Use

The quick collection of information and warning messages for specific areas of the system is normally part of the daily system administration work. For most problem situations, only a fraction of the information available in the monitor is required. For database problems, for example, you only need to work with the monitoring tree elements for the monitoring of the database.

There are therefore different monitors for the Alert Monitor, that each display information for an aspect of system management. These monitors are grouped into monitor sets. Within the monitoring architecture, you can create, copy, and edit monitors yourself, and transport monitors to other systems. In this way, you can create monitors that contain precisely the information that you need for your daily work. You can save and reuse all of your own monitors.

As the definition process is quick and easy, you can use a monitor of your own not only as a long-term, specialized work center, but also for short-term problem analysis or special monitoring. If, for example, you want to monitor the response time of a particular server, you can define a temporary monitor that monitors the response time, CPU utilization, and other relevant parameters for this server.

During the definition of monitors, you can use not only the existing nodes, but also virtual nodes and rule nodes. A virtual node structures the monitor; it is a heading or a description for the nodes created below it. A virtual node does not have a monitoring function itself.

A rule node specifies a rule that defines what should be included in the new monitor. The monitoring architecture interprets the rule and includes in the monitor the nodes that fulfill the selection criteria in the rule. The rules are regularly reinterpreted, so that your own monitor automatically corresponds to the current system landscape. A monitor defined with rules will, for example, automatically include a newly started SAP application server.

SAP deliver a range of predefined standard monitor sets with the SAP system. The standard monitors contained in these sets provide system administrators with a complete overview of the system and ready-to-use views for special tasks such as monitoring the database, background processing, the operating system, the system log, and the spool system. There is even a monitor for monitoring the monitoring architecture (CCMS Selfmonitoring).

Definition

As a system administrator, you can conveniently monitor your system with monitor sets. A monitor set contains several monitors. In turn these monitors consist of subtrees of all available objects. You can group the monitors according to task, by setting up several monitor sets in parallel.

You can either create the monitor sets temporarily, in order to solve a problem and then delete them, or you can store them permanently in the system.

Use

The SAP System contains three predefined standard monitor sets:

· SAP CCMS Monitor Templates

The monitors in the SAP CCMS Monitor Templates monitor set display the monitoring objects and attributes that are crucial for the monitoring of your SAP systems and which are used for normal system administration.

· SAP CCMS Technical Expert Monitors

Use the monitors in the SAP CCMS Technical Expert Monitors monitor set to monitor the monitoring architecture itself and to analyze problems in this area.

For example, you can use the CCMS Selfmonitoring monitor for internal monitoring or All Monitoring Contexts to view all available contexts in your systems.

· SAP CCMS Monitors for Optional Components

Use the monitors in this set to monitor components that are not part of the standard SAP system.

See also:

Creating and Editing Monitor Sets

Transporting Monitor Sets and Monitor Definitions

The following section describes the most important elements of the Alert Monitor and their relationships to each other.

Purpose

When you start transaction RZ20, the system first displays the monitor sets available to you. These monitor sets group the monitors.

A monitor set usually consists of different monitors. A monitor is a collection of monitoring tree elements (MTEs) in a hierarchical structure that deliver information for a particular aspect of system management.

The hierarchical structure of a monitor is the alert monitoring tree. In this tree, you can check the status of your IT system landscape. The MTEs are nodes of this tree, where the root node also has the name of the monitor.

Different MTEs are Elements of the Alert Monitoring Tree: monitoring summary nodes, monitoring objects, and monitoring attributes. Monitoring summary nodes (summary MTEs) provide a better overview in the tree, without performing a monitoring function themselves.

A monitoring object represents a component of your IT environment that you want to monitor (such as the CPU of a server or background processing), while a monitoring attribute displays a value, status, or text that is reported for this object (for example, the CPU utilization during the last 15 minutes).

If a value that deviates from the norm is reported for a monitoring attribute, the Alert Monitor generates an alert. The conditions under which an alert is generated, the criticality of the alert, or which message is assigned to an MTE – all of these are properties of an MTE.

In addition to its properties, an MTE has methods: the data collection method allows the collection of information about the MTE, the auto-reaction method and analysis method are executed as a reaction to an alert.

To simplify Customizing, the properties and methods do not need to be edited for each MTE individually: There are attribute groups for attributes, and MTE classes for objects.

Operation and Customizing of the Elements of the Alert Monitor

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).

The monitoring architecture displays a tree in the Alert Monitor that contains all monitoring tree elements (MTEs) for your monitored systems. The elements are clearly structured and arranged in the tree. There are three types of MTEs:

· Summary MTEs (Monitoring Summary Nodes)

These act as titles or headings in the alert monitor and do not have any monitoring functions themselves. No alerts can be triggered for summary MTEs. However, alert statuses and messages can be displayed.

There are two kinds of monitoring summary node:

¡ Real monitoring summary nodes: are stored in the monitoring segment

¡ Virtual monitoring summary nodes (): are not stored in the monitoring segment, but exist only to provide a clearer display of real MTEs in a monitor

· Monitoring objects ()

Monitoring objects are particular components of your systems that the monitoring architecture monitors (such as SpaceManagement or CPU). They are created by the data suppliers. The objects combine various monitoring attributes that belong to the same component or the same attribute of a system.

· Monitoring attributes

Monitoring attributes are data types that can be reported for a particular monitoring object. The monitoring object CPU, for example, has the attributes CPU utilization and 5MinuteLoadAverage. A data supplier reports data for these attributes, and the alert monitor triggers alerts for the attributes if the data violates the defined alert thresholds.

See also:

Alert Monitoring Tree

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