SAP Library - Find your answers

Displaying Report Properties

Use

You can use Central Performance History Reports (CPH) to display selected performance values of the CPH directly or as a job. When you do this, the report itself (for example, when executed on the screen) does not contain the complete header data of the report ‑ such as the settings of the Report Definition or the execution time of the report.

You can find this information in the report properties. You can also edit the report properties to add your own remarks, and save the properties as a local file. No changes to the text have any effect on any function of the CPH.

Procedure

...

1. You can display the report properties from several functions:

¡ In the Report Browser, choose the desired report by double clicking it, and choose the Report Details pushbutton.

¡ Execute a report directly on the screen (see Scheduling and Executing a Report), and choose the Report Detailspushbutton.

2. In both cases, a screen appears on which the report properties are displayed. The screen has the following structure:

3. To save the report properties as a local file, choose Save as a Local File ().

Central Performance History of the Monitoring Architecture start page

Log attributes (icon ) are monitoring attributes that capture messages in their context. This means that the data collection method does not just write isolated messages in the Alert Monitor, but also the content of a log or trace.

Features

Log attributes have a number of special features in the display of properties and methods. These are described here. If you want to display the properties of a log attribute, select the attribute in the alert monitoring tree and choose Properties.

Display "Current Value" like Group Box

Alert Settings Group Box

Internal Storage of Message Lines Group Box

See Also:

Detail Display for Log Attributes

Monitoring objects and attributes are assigned various properties and methods. There are default settings in the standard SAP System (which is delivered with the properties variant SAP_DEFAULT) for most nodes for properties and methods, meaning that you can already work with these settings.

Auto-reactions are an example. There are very few assignments of these in the standard SAP System. You can make your own assignments of these (see also: Selected Methods of the Alert Monitor).

If the standard settings do not meet your requirements, you can change the properties and method assignments at any time. You can make the changes both in the Alert Monitor and in the Customizing transaction RZ21. You can either make changes for the individual node itself or for the MTE class or attribute group, to which the node belongs (we recommend the latter).

Features

The following cases occur most often in practice:

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

Use

Status attributes (symbol ) are monitoring attributes that report error message texts and alert status.

Features

Status attributes have a number of special characteristics in the display of properties and methods. To display the properties of a status attribute, choose the attribute in the alert monitoring tree and choose Properties.

When should a message trigger an alert?

• Always (at every message): The Alert Monitor triggers a alert with the corresponding message value for every message.
• Message value (color) has changed: The Alert Monitor only triggers an alert if the alert color of a reported message changes. For example, an alert is triggered if a red message follows a yellow message.
• The message sent has changed: The Alert Monitor only triggers an alert if the color or severity of a message changes or if a new message is sent.
• Never: The Alert Monitor does not trigger any alerts.

Changing the value for alert generation

Use

Performance attributes (symbol ) are monitoring attributes that collect certain reported performance data and calculate the average.

Features

In the display of the properties and methods, performance attributes have a number of special characteristics that are described here. To display the properties of a performance attribute, choose the attribute in the alert monitoring tree and choose Properties.

Comparison Value

Threshold values

In this group box, you can edit the threshold values with which an alert is triggered if the reported value exceeds or falls below the appropriate value. Note when doing so that the change applies not only to the concrete monitoring tree element (MTE), but for the whole MTE class. This is displayed at the top of the screen.

You have the option to assign different threshold values for a Change from GREEN to YELLOW and the Reset from YELLOW to GREEN (the same also applies for the Change from YELLOW to RED and the Reset from RED to YELLOW). This prevents a constant switching between the alert levels, if the attribute is wavering around the threshold value, which would generate a new alert every time.

The display of a rule of this type would look as shown in the graphic below. To find out the alert level, start from any value for the performance attribute and move upwards until you meet the curve. If the value is climbing from a lower alert level, the lower part of the curve is valid for determining the alert; if the value is falling from a higher alert level, the upper part of the curve is used.

The unit of the threshold value is determined using the data supplier.

Explanation for an Alert

If an alert is triggered, it is displayed in the Alert Browser. A short explanatory text for the alert is displayed there in the Alert Text column. Choose the relevant line of an alert and choose F1 to display a more detailed text about the alert. The system displays its short text and the associated message class and number here. You can use these to adjust the delivered message texts.

Every monitoring tree element (MTE) has properties that contain more detailed information about the element. The properties are divided into two groups:

· Properties that depend on the type of the MTE; these are:

Properties of Log Attributes

Properties of Performance Attributes

Properties of Status Attributes

· Properties that are independent of the type of the MTE. These are called general properties.

The general properties of an MTE include a message class and message number; these contain a short description of the MTE. The general properties also contain information about possible alerts. However, as alerts can only be generated for monitoring attributes, the following properties apply only for the attributes that belong to the object:

· Criticality and severity of the alert that is associated with the MTE

· Maximum number of alerts to be stored for this MTE

· Conditions under which no alert is to be generated

By default, the properties for the different MTEs in an MTE class are identical, however, you can change the properties individually for single MTEs (see Changing Properties and Maintaining Methods).

Use

The general properties determine, above all, the handling of alerts. If alerts for particular MTE classes or individual MTEs are especially important for the monitoring of your IT landscape, you can ensure that these alerts are, for example, reported further up the alert monitoring tree, or that a large number of these alerts is stored in the monitoring segment, by changing the general properties.

Structure

The general properties are as follows:

The number and selection of alerts that are to be stored have a critical importance for the function of the monitoring architecture: incorrect settings can cause the monitoring segment in which the alerts are stored to become full. We therefore recommend:

§ You should store the newest alerts. You can use the report RSAL_KEEPALTYPE_MODIFY to change all occurrences of All alerts should be kept to the newest alerts should be kept. Execute the report once for each affected SAP system and after every upgrade of the monitoring architecture.

§ You should complete alerts regularly to gain available storage area in the monitoring segment. With a large number of MTEs, it is useful to define conditions under which the system should automatically complete alerts.

§ Observe the Space subtree of the CCMS Selfmonitoring monitor. If there is insufficient free storage space in the monitoring segment, a corresponding alert is generated there.

Keyword: BASIS
Title : Changing SAP MaxDB Database Properties