CCMS Monitoring : Creating and Changing Monitors

You can quickly and easily create your own monitors that meet your own specific requirements. If, for example, you want to monitor the relationship between your CPUs, operating system paging, and the dialog response time of your SAP systems, you can create an alert monitor that contains only these monitoring tree elements (MTEs). You can decide whether this monitor covers one or more systems.
To be able to create a monitor, first create a tree structure. You have the following options for the individual nodes:
· Static MTE Selection
You can explicitly select MTEs for your monitor. Only the selected MTEs are added to the monitor, and the selection of the MTEs is not updated.
· Rule-Based MTE Selection
You can also use rule-based MTE selection (dynamic selection) to create your monitor. In this case, the alert monitor includes all MTEs that fulfill a certain rule in your monitor. If the MTEs that meet this rule change, the system automatically updates your monitor. In this way, your monitor is automatically updated if a new system is added to the alert monitor.
You can combine both static and rule-based MTE selection in the same monitor.
· Virtual MTEs
You can define virtual MTEs to structure your monitor. Virtual nodes are used as titles or labels in the alert monitor. They have no function other than to group monitoring tree elements visually. For example, you can create virtual MTEs as titles for different groups of real MTEs in your monitor.

To be able to create or change a monitor, you must first activate the maintenance functions.

Procedure
1. Choose CCMS ->Control/Monitoring -> Alert Monitor, or call transaction RZ20.
2. Choose Extras -> Activate Maintenance Functions.
3. Choose one of the functions from the below list:
Create monitor
Choose the monitor set in which you want to create the monitor; ensure that it is a monitor set that you can modify ( ); choose Monitor (set) -> Create ( ).
Change monitor
Expand the monitor set and choose the monitor that you want to change. Choose Monitor (set) -> Change ( ).
You can also change a monitor that has already been started by choosing Monitor -> Change ( ).
4. The alert monitor displays the complete monitoring tree. The system displays the name of the monitor in the top line of the tree. You can now either add MTEs to your monitor or display the properties of existing MTEs. To do this, choose one of the functions from the table:

Insert static MTE selection
Select the desired MTEs from the list of Selectable MTEs . Only the selected MTEs will be visible in the completed monitor. The system displays the list at every point in the monitoring tree where you can insert statically created MTEs.
Insert rule-based MTE selection
Choose the node under which you want to insert a rule-based node; choose Edit -> Create Node ( ) and, on the Create Node screen, choose the Rule Node radio button
Insert a virtual MTE
Choose the node under which you want to insert a virtual node; choose Edit -> Create Node ( ) and, on the Create Node screen, choose the Virtual Node radio button. Enter a name for the node.
Change node
Select the relevant node; choose Edit -> Change Node ( ). You can change different properties, depending on the type of the node.
Display node
Select the relevant node; choose Edit -> Display Node ( ). The system displays different properties, depending on the type of the node.
Delete node
Select the relevant node; choose Edit -> Delete Node ( ). The node is deleted, along with its subnodes.

The following rules apply to the sequence of nodes in the monitoring tree:
· The root node (top node) of a monitor is always a virtual node. Its name is the name of the monitor.
· You can create as many layers of virtual MTEs as you wish. A virtual node can only be placed under a rule node or another virtual node in the tree hierarchy.
· A rule node can only be placed under a virtual node or another rule node in the tree hierarchy.
· A static node can only be placed under a virtual node.

5. Save your monitor by choosing Monitor Definition ® Save or Generate Monitor ( ). If you are creating a new monitor, the system prompts you to enter a name for your monitor.

CCMS Monitoring : MTE Classes and Attribute Groups

The alert monitoring tree consists of individual monitoring tree elements (MTEs). They are either components of your IT landscape that are to be monitored (monitoring objects), or values, statuses, or texts that are reported for these objects .These MTEs are assigned to MTE classes and attribute groups in the monitoring architecture:
· An MTE class describes the general properties and method assignments that are common to a particular group of monitoring tree elements.
· An attribute group describes the common threshold values for alerts for a particular attribute type.

MTE classes and attribute groups simplify the Customizing of the Alert Monitor, since you do not need to change threshold values, properties, or methods individually for every MTE, but only for the corresponding attribute group or MTE class.
MTE classes also simplify the creation of your own rule-based monitors, since you do not need to specify every MTE individually when constructing the alert monitoring tree, but rather only the corresponding MTE classes.
The classification of the MTEs to MTE classes and attribute groups is already fully predefined. You do not need to make any changes to be able to use this classification.

If you want to change the properties, methods, or threshold values, the system displays a message informing you whether the change refers only to an individual MTE or to the corresponding MTE class or attribute group. You can change this default value

· MTE Class:
The Space Management monitoring object and the Free Space monitoring attribute both belong to the MTE class CCMS_DB_Freespace_MT. This means that both MTEs have the same general properties and method assignments.
· Attribute Group:
All instance-specific occurrences of the Response Timemonitoring attribute belong by default to a single attribute group. This means that the same threshold values are set in all of the instances of a system and that changes to the threshold values apply to all instances.