CCMS to Technical Monitoring Migration: Use case – Monitoring OS Processes in Technical Monitoring

Background: This document explains how to migrate the monitoring data from CCMS to Technical Monitoring. In this document I have explained on how to setup new custom metrics and alerts in Technical Monitoring using CCMS migration approach. In the below example the monitored process “UnixInetd” is configured in Technical Monitoring, the data provider being the MTEs of RZ20 Architecture.

1) Locate the metric in the RZ20 monitoring tree

Run transaction RZ20

Select the monitor set “SAP CCMS Technical Expert Monitors” > “All Monitoring Contexts”, or an other set which contains the desired metric.

Expand the monitoring tree to the desired metric

Select the metric and click on “Properties”

This screen shows all information that are needed to define a new MAI metric: the full MTE name (field “Properties of”) and the MTE class.

The full MTE name of a CCMS metric has the following structure:

<System ID> \ <context name> \ <path elements> \ <object name> \ <attribute name>

In our case:

SID\xxxxxxx\OperatingSystem\Monitored Processes\UNIXinetd\<all users>: Process Count

The MTE class is not part of the full MTE name, but a separate property <MTE class> = UNIXCount

So note down following two informations from RZ20:

<object name> = UNIXinetd

<MTE class> = UNIXCount

That’s all the information we need from RZ20. Let us go to Technical Monitoring setup to complete further activities. This setup is done at Technical System level template.

2)Create a custom alert in Template Mainteinance in solman_setup.

Press the “Create” button and select in the drop-down box “Alert”

A “Custom Alert Creation Wizard” will open. On the “Overview” tab provide a “Name” for the alert and specify the “Category” of the alert. Make sure that you select the same category the metric you want to monitor will have. Otherwise you will not be able to assign your metric to the alert.

Switch to the “Others” tab and provide a “Technical Name” for the alert.

Press the “Next” button. As we did not create a metric yet there is nothing to assign.Press the “Finish” button to close the wizard. A notification will inform you that you have to save in order to persist your change.Press the “Save” button” to persist your custom alert.

3) Create a custom metric on Technical System level

In your custom template press the “Create” button and select in the drop-down box “Metric”A “Custom Metric Creation Wizard” will open. On the “Overview” tab provide a “Name” for the metric and specify the “Category” of the metric.

Switch to the “Data Collection” tab. You have to specify the following values:

Collection Interval – 1 min

Data Collector – Pull RFC Collectortype

Data Provider – CCMS System Wide MTEs

Mention the details you noted down before from RZ20.

OBJECT_NAME = UNIXinetd

MTE_CLASS     = UNIXCount

Switch to the “Threshold” tab a specifiy a useful threshold. In the “Others” tab and specify a “Technical Name”

Press the “Next” button and assign the prviously created alert “Monitored Daemon Process Availability” to this custom metric. Press the „Finish“ button and save the “Save” changes.

Once the template updation is done you need to select the system for which the monitoring to be activated in “Define Scope” tab. Assign and activate your new template in ” Setup Monitoring tab”. Now the newly created metric and alert are available in System monitoring.

Regards

Vivek Hegde