The Health Monitoring app (formerly Open Component Monitoring) supports Advanced System Management by providing additional monitoring metrics that go beyond standard system monitoring. Use Health Monitoring when configuration differs vastly between managed objects. In addition, Health Monitoring is used to provide low-barrier monitoring for managed objects that are not included in the landscape management database (LMDB).
Health Monitoring provides the following types of metrics for monitoring managed objects:
For all metric types except Cloud Service metrics, the monitoring data of a metric is collected by a Simple Diagnostics Agent (SDA). Depending on the type of metric, an SDA is used which is either installed on a host of the monitored object or on a host in a collection group in which the monitored object is located.
A collection group corresponds either to a customer network or to a subnetwork of a customer network. Collection groups of the first kind are available in Health Monitoring automatically if the relevant customer networks are defined in SAP Focused Run. You can create, change, and delete collection groups of the second kind in the Health Monitoring app.
In the case of Cloud Service metrics, how monitoring is performed depends on the type of collection involved. With pull data collection, monitoring is by means of integration with the Expert Scheduling Management Cockpit and an ABAP collection job (frequency: five minutes). With push data collection, the managed service sends the metrics directly to the Health Monitoring app.
Many Health Monitoring metrics are unmodeled, which means they are not assigned to a specific technical system in the landscape. Nevertheless, they need to be executed by a Simple Diagnostics Agent, which must be located inside the collection group. It is therefore necessary, as a first step, to define a central Simple Diagnostics Agent in the collection group which should execute the Health Monitoring metrics.
To activate a collection group, proceed as follows:
Perform the following steps to create a new Health Monitoring metric:
If you have to create or change multiple Availability metrics simultaneously, you can use the mass maintenance functionality in Health Monitoring (available since SAP Focused Run 3.0 SP00).
For further details, see the relevant guide Mass Maintenance of Availability Metrics in Health Monitoring:
For details of how to create OS Script metrics, see the document Creating OS Script Metrics with Health Monitoring.
Here is a list of the parameters used by all metrics except Cloud Service metrics in the Health Monitoring app. For information about Cloud Service metrics, see here.
|Metric Name||A descriptive name for the metric. It is advisable to choose a name that can be easily understood by others.|
|Collection Group||The collection group in which the metric is created|
|Collection Interval/ Collection Frequency||How often the metric is collected|
|Threshold||The metric threshold. For each metric, you specify a threshold and what happens when this threshold is reached – for example, set status of metric to red (error).|
|Metric Documentation||Additional information about the metric|
|Alert Active||Parameter that allows an alert to be triggered when the metric fails|
|Alert Name||The name of the alert. It is advisable to choose a descriptive name that can be easily understood by others.|
|Severity||Severity of the alert in Alert Management. Maintain a value between 0 (very low) and 9 (Critical).|
|Notification Variant (optional)||Selection of notification for sending an additional e-mail for the alert, if required|
|Additional Attributes||An attribute and an attribute value (optional) add additional information to a metric. You can also add multiple attribute/value pairs to a metric. For example, you could specify an attribute SID and an attribute value FRN for a metric to specify that this metric refers to an SAP system with the system ID FRN. You can use additional attributes to group the data displayed (for example, in the Attribute Overview tab or in a table).|
|Outbound Connector Variant (optional)||Selection of outbound connector for forwarding the alert via BAdI implementation, if required|
For details of individual metrics and their additional parameters, see here.
As of SAP Focused Run 3.0 SP03, a modeled approach is provided for monitoring cloud services maintained in the Cloud Services Management app. The following types of cloud services are supported by SAP Focused Run 4.0 SP00:
These services are monitored using an overview of metrics grouped on cards.
For the services that perform pull data collection, monitoring is by means of integration with the Expert Scheduling Management Cockpit app and an ABAP collection job (frequency: five minutes). For the services that perform push data collection, the data is sent to the Health Monitoring app directly from the managed service.
To find out more about configuring cloud services, see Configuration of Cloud Services for Health Monitoring.
You can create the following metrics to monitor the availability of a Groupware Connector Server:
Create a new Windows Services metric with the following parameters:
Create a new Windows Services metric with the following parameters:
Other configuration examples are available in our SAP Focused Run - Internet Demo System.
The SAP_FRN_OCM_HOUSEKEEPING job deletes data that is no longer required from the Health Monitoring database tables (see the Master Guide for SAP Focused Run). The housekeeping job runs once a day.
To view the status of the last run and the scheduled date/time of the next run, proceed as follows:
In the Health Monitoring app, choose the Configuration button (gear icon) at the top right of the screen and then open the Infrastructure panel.
As of SAP Focused Run 3.0 FP03, it's no longer necessary to configure housekeeping via the database. The Configuration area of the UI, containing the Infrastructure panel, now also includes a Housekeeping section.
The configuration tables are divided into two sections: Raw Data and Aggregated Data.
The value in the Raw Data field specifies how long monitoring data is kept in the Health Monitoring database tables – for example, 180 days. In this case, any monitoring data required for detailed or collector charts that is older than today minus 180 days is aggregated and deleted. Other raw data is simply deleted.
The value in the Aggregated Data field specifies how long aggregated monitoring data is kept in the Health Monitoring database tables – for example, 720 days. If the aggregated monitoring data is older than today minus 720 days, it is deleted.
If you've already customized raw data and aggregated values in an earlier feature pack, your legacy values are still available. The UI always displays the lowest configured value. If you make any changes to values on the UI, all values that depend on the relevant type (raw or aggregate) are updated.
To maintain housekeeping, change the values in the Housekeeping section of the Configuration panel and save them.
You can maintain the housekeeping settings for each of your SAP Focused Run systems, or you can transport the settings – for example, from a test system to a production system. To transport settings, go to transaction SM30 (Extended Table Maintenance), enter OCM_HKCONFIG in the Table/View field and choose the Maintain button. Next, select the table rows and choose Table View > Transport to store the settings in a Customizing request. You can now transport the Customizing request from your test system to your production system, for example.
If you adjust the housekeeping configuration, it's advisable not to make large changes (for example, double-digit reductions to the number of days).
If changes of this kind are unavoidable, be aware that housekeeping will be done step by step to avoid performance issues.
This means that aggregation will be done over a period of days until the change has been taken into consideration.
For example, if you change the housekeeping value from 180 to 100 days, housekeeping will run over a number of days until the difference between the oldest database entry and the newly configured value no longer affects performance.
While we strongly recommend using the new Configuration panel on the UI of the Health Monitoring app, you can still configure housekeeping settings via the database, as in earlier feature packs.
To maintain housekeeping settings in database table ocm_hkconfig, do the following: