Skip to end of metadata
Go to start of metadata

Summary

All your applications have a process on OS level as a baseline. Making sure this process is running smoothly is a first step to monitor the availability of your application. With the OS Collector SAPOscol the monitoring of processes is possible since a long time. In the older days, these monitored processes were visible in CCMS. This guide describes how you can leverage the process monitoring capability of SAPHostAgent with SAP Solution Manager 7.2 Monitoring and Alerting Infrastructure and create custom metrics to monitor the processes of your SAP and non-SAP applications.

Prerequisites

1) Install a Diagnostics Agent and SAP Host Agent in the target server

The Diagnostic Agent and SAP Host Agent are required to monitor the status of the OS process. The Diagnostics Agent use a SAP Host Agent feature to get the OS process information from the host. Refer to the Diagnostics Agents WIKI page for details about the installation of the Diagnostics Agent and SAP Host Agent.

2) Create a Technical System In LMDB

In case the target system to be monitored is a non-SAP system and doesn’t have SLD data suppliers, the system will need to be manually created in the Solman LMDB.  How to create a non-SAP system in LMDB is described in the guide “Creating Unspecific Cluster System” under System Monitoring - How-to Guides.

General Steps

 

1) Decide to Create a Custom Monitoring Template, or choose the target custom template to add the metric

To monitor a custom OS process using the SAP Solution Manager Monitoring and Alerting Infrastructure it is required to add a custom metric in the monitoring template that will be configured/activated for the target system.

2) Create Custom Metric for the Monitored Processes

To monitor a custom OS process using the SAP Solution Manager Monitoring and Alerting Infrastructure it is required to add a custom metric in the monitoring template that will be configured/activated for the target system.

The data collector to be used for the metric is 'SapHostAgent GetProcessInfo' collector. The data collector has the following configurable parameters:

ParameterMeaning
COMMANDLINE*Not required (leave empty)
PROCESS_PATTERN (mandatory)the name of the process(es) as regular expression
KEY_FIG (mandatory)an individual property of the process information, the following properties are available
  • CPUUtilization \(%\)
  • PrivPages \(KB\)
  • ResidentSize \(KB\)
  • NumberOfProcesses
USEROS User Name

The custom metric can be added to an existing custom template or it is possible to create a new custom template to define the metric. If the target managed system is a non-SAP system, then create a custom template derived from "Generic Product Version". The picture below shows an example where to find the "Generic Product Version" monitoring template:

After create the custom monitoring template, it is possible to create/add the custom metric for the OS process monitoring.

To create the custom metric, change the view to 'Expert Mode'

After switch to 'Expert Mode', it is possible to create the metric. Click on 'Create' then 'Metric':

Fill the required information in tab 'Overview':

The technical name should start with Z.

On the Data Collection tab: select the data collector (SapHostAgent GetProcessInfo) and its properties to monitor the target process. Make sure that the process name is defined as regular expression . For wildcard this means, instead of using “*” you must use “.*”.  The properties need to be defined are:

  • Data Collector Type: Diagnostics Agents (push);
  • Data Collector Name: SapHostAgent GetProcessInfo;
  • KEY_FIG: Select the target key figure (NumberOfProcesses, Total CPU Time (%), Total Memory (KB), Total Memory  (MB), Total PrivPages (KB),  Total PrivPages (MB));
  • PROCESS_PATTERN: OS process name as regular expression;

The picture below shows an example that will monitor the number of processes active which contain 'wrapper' in its name:

On the tab Data Usage you decide whether you want to use the data for alerting (Send values to Event Calculation Engine) or for reporting (Send values to SAP Netweaver Business Warehouse). 

On tab Threshold choose the threshold according to the metric configuration.

In this example (NumberOfProcesses), the value which is returned by the data collector is an integer value hence the 'Numeric Threshold' needs to be used. The example below shows the threshold 'Number Threshold (Green/Red)' that will be triggered if the value 'Falls below or equals threshold'. If the number of process is equals 0 (zero) an alert will be triggered.

Finally, click on Next button and then finish the metric creation:

3) Create Custom Alert for the Monitored Processes

After create the metric definition it is required to create the Alert definition, for this click on 'Create' and then choose 'Alert':

Define the alert details:

  • Name: Alert name
  • Category: The category of the alert (Availability, Performance, Exception, Configuration, Self-Monitoring).
    NOTE: The alert category must be the same of the category of the metric create, otherwise the alert cannot be assigned to the metric.
  • Severity: Alert severity
  • Technical Name: Technical Name of the alert, must start with Z

Click on 'Next'.

IMPORTANT: In step 'Assignments' select the metric that was created before, in this case 'Sampe OS Process Monitoring'. This will assign the metric to the alert.

Click on 'Finish' to finish the alert creation.

In tab 'Metrics, Events, Alerts Hierarchy' it is possible to confirm whether the alert and metric are indeed assigned to each other. Example:

4) Assign the Custom Template to the Target Managed System

Finally after create the Custom Metric and its Alert in a custom template, it is required to perform the System Monitoring configuration for the target system to activate the new system monitoring teamplate.

Go to the System Monitoring configuration, in step 'Define Scope' and choose the target system:

Assign the custom template created for the Custom OS Process Monitoring to the system:

Finally, perform the System Monitoring activation.

5) Results in System Monitoring

Finally after the configuration and activation of the custom template, in the System Monitoring application the custom metric will be shown under the System Availability node:

 

 

  • No labels