Rule MTEs: Rule Descriptions and Use  

Definition

The rule-based monitoring tree element (MTE) technology of the alert monitor allows you to create your own monitors. Rule based monitors have the following qualities:

Rules enable dynamic selection of sets of MTEs according to selection criteria. The other way to create your own monitor (static selection, where the alert monitor is not automatically updated if the system infrastructure changes) enables you to choose single MTEs explicitly.

Use

When you create a rule MTE, you choose a predefined rule for selecting MTEs for your new monitor. The alert monitor interprets the rule and chooses the MTEs that meet the selection criteria that you have specified. The following MTE rules are available:

MTE Selection Rules

Creates virtual MTEs for R/3 Systems that have been included in the alert monitor.

The selection options include ALL (all available R/3 Systems); CURRENT (R/3 System in which the alert monitor is running), and specific systems by name. You can also include in your monitor those systems that you have defined as PRODUCTIVE or TEST systems in your system landscape.

You use this rule to set up rule-based monitoring across one or more R/3 Systems. Rule MTEs that you add below this MTE are interpreted for each system that you have selected. You add monitoring functionality by creating virtual and/or rule MTEs under this MTE.

This rule inserts monitoring functionality by MTE class. The <MTEclass> parameter lets you add monitoring functionality by MTE type: CPU, response time, background, and so on. The MTE class is displayed as a real node in the monitoring tree, that is, the MTE is monitored by the alert monitor.

All monitoring objects and attributes are associated with MTE classes. Examples: The ResponseTime monitoring attribute is assigned to the MTE class R3DialogResponseTime; AbortedJobs is assigned to MTE class R3BPServerSpecAbortedJobs.

Since all instances of a particular MTE share a single MTE class, the class selection rule lets you select monitoring objects across SAP instances and systems. For example, you can create a monitor for dialog response times in all SAP instances.

You use this rule to add monitoring functionality to your monitor by monitoring object type and attribute.

Adding MTEs by class also adds any subordinate MTEs. Example: Adding the MTE class "CPU" also adds the subordinate MTEs CPU_Utilization and 5minLoadAverage, even though these MTEs have different MTE classes.

You can display the MTE classes that are available using the F4 help. This does not display where an MTE class appears in the monitoring tree, so it can be hard to find the MTE class that you want. To do this, open one of the standard monitors of the MTE that you want to include in a monitor. Then choose Properties to display the MTE class of the MTE.

Use these two rules in conjunction. They return the same results as the CCMS_GET_MTE_BY_CLASS rule, but the information you require is displayed in a more clearly structured form.

When you select the CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL rule, use the <MTEclass> parameter to include the MTE class as a virtual node in the tree. (Virtual nodes are used as "headings" under which you can group MTEs.

You then select the CCMS_GET_MTE_BY_CLASS_UNDER_CLASS rule. In the <ChildMTEclass> parameter, you then specify the MTE classes that you want to monitor as real nodes in your monitor.

You may also see two additional rules. These are CCMS_GET_MONITORING_SEGMENT_NAMES and CCMS_GET_MONITORING_CONTEXT_NAMES . These rules are intended for SAP-internal use only. Although you can experiment with them, SAP recommends against trying to use them in your own monitor definitions.

The rule CCMS_GET_AVAILABILITY_FOR_SYSTEM is reserved by SAP for future use.

Notes

Interpretation of stacked rule MTEs: If you have stacked rule MTEs (that is, inserted CCMS_GET_MTE_BY_CLASS under CCMS_DEFINE_R3_SYSTEM ) then the subordinate rules inherit the SYSTEM specification in the primary rule.

Example: If you specify <ALL> for CCMS_DEFINE_R3_SYSTEM , then subordinate "MTE_BY_CLASS" rules also select from <ALL> R/3 Systems.

The effect: Your monitor is structured by R/3 System. Under each system entry in the monitoring tree, you will find the MTE_BY_CLASS selection for that particular system.

Periodic update: The alert monitor periodically re-evaluates the rule MTEs in your monitor. This ensures that changes in the system environment, such as the start-up or shutdown of an R/3 instance, show up in your monitor.

Construction restrictions:

 

For more information, see: Creating Your Own Monitors.