In this example, you integrate the CCMS metric SAP Update: Mean Waiting Time in Dispatcher Queue
into technical monitoring. The metric measures the the time which the update requests spend in the dispatcher queue before being assigned to a free work process.
You can display this metric in the Alert Monitor, e.g. in the Entire System
monitor.
This section is an example of the Extend Monitoring and Alerting Infrastructure with CCMS Metrics process. This process shows how you can extend technical monitoring with additional, previously not monitored CCMS metrics.
The integration of the CCMS metric into the Monitoring and Alerting Infrastructure (MAI) comprises several steps, which are described consecutively below:
To integrate the CCMS metric into MAI, you need a set of technical attributes of this metric (this step, and its attributes, are described under Determine CCMS Metric Attributes). You need the following attributes:
MTE class
Object name, if the metric occurs more than once per context
Context name
MTE Type
Granularity
Instance-specific or system-wide
To determine these attributes for the metric, proceed as follows:
Start the Alert Monitor (transaction RZ20) in a managed ABAP system, and start the
monitor.Expand the monitor paths Queue Time
. Choose Attributes
.
Note
The monitor tree also contains the object PerformanceU2
, which also contains a node with almost the same attributes. So the MTE class doees not uniquely determine an MTE in a context.
The Monitoring: Attributes and Methods
screen displays most of the required attributes. The name of the MTE class is R3UpdateQueueTime
, the long name of the node is:
<system ID>\<instance name>\R3Services\Update\PerformanceU1\QueueTime
Results:
Attribute | Value |
---|---|
MTE class |
|
Context |
|
Object Name |
Note You must create two metrics with different object names for the MAI integration. End of the note. |
MTE Type | Performance attribute, so a numeric value is output |
Granularity | Select the node in the monitor tree and choose ( |
You have then determined all required attributes of the CCMS metric.
To integrate a CCMS metric into MAI, you must specify the data collector and its input parameter for the metric. The collector and its input parameter value depend on the CCMS metric attributes that you determined.
This step is described under Determine the Collector. Use the data collector CCMS MTE + Object Name
, because the metric has the following attributes:
It is an instance-specific metric.
The metric delivers a numerical value.
The object name is relevant.
The input parameters are as follows:
Parameter ID | Parameter value |
---|---|
| 5 minutes |
|
|
|
|
| This parameter is filled automatically |
MAI metrics, whether delivered by SAP or created by customers, are in templates in technical monitoring, so to create a metric, you must first create a customer template in der SAP Solution Manager Configuration
(this and the next step are described in Creating MAI Metrics from CCMS Metrics). To do so, proceed as follows:
Start SAP Solution Manager Configurations
(transaction SOLMAN_SETUP).
Go to Technicals Monitoring
, the monitoring use case System Monitoring
, and step Template Management
.
Switch to editing mode.
Expand the type of the managed object and product for which you want to create a custom template, in the Templates
navigation bar. For an instance-specific metric, it is
If you have not yet created a suitable template, select this SAP-delivered template, and choose Create Customer Template
. Enter a name in the Name
field, for example Other CCMS Metrics.
Save the template.
You have now created a customer template. Create the metric in this template.
You are in Template Management, and have created a customer template. Create a new MAI metric in this template:
Go to edit mode, and then to expert mode.
To create a new metric, choose
. A customer metric creation wizard starts.Enter the general attributes of the new metric in the Overview
tab:
Attribute | Value |
---|---|
| Queue Waiting Time Update1 |
|
|
|
|
|
|
|
|
| Do not change this entry. |
| Z_R3UPDATE1QUEUETIME |
| Enter a description of your metric. |
Go to the Data Collection
tab. Specify the technical connection to the CCMS metric to be integrated into MAI:
Attribute | Value |
---|---|
|
|
|
|
|
|
|
|
Go to the Data Usage
tab. Specify the applications for which you use the new metric. In this example, you want to display the history of the new metric in the metric monitor as well.
Attribute | Value |
---|---|
| Do not change this entry. |
| Set this flag. |
|
|
|
|
Go to the Threshold Value
tab. Specify the threshold types and values for the new metric:
Attribute | Value |
---|---|
|
|
| Do not change these entries. |
Threshold values | Copy the threshold values from CCMS:
|
Go to the Validity
tab. Do not enter a value.
Go to the second step (Assignments
) of the customer metric creation wizard. You can assign an alert to the metric. Skip this step because there is not yet a suitable alert for the new metric. Choose Finish
, to complete the creation of the metric.
Save the template.
Note
Create another metric analogously, because you need two MAI metrics for type 1 and type 2 updates. The differences from the metric just created are:
As the metric Name
, specify Queue Waiting Time Update2.
As the Technical Name
of the metric, specify Z_R3UPDATE2QUEUETIME.
As Input Parameter Collector
for OBJECT_NAME
, specify PerformanceU2.
No alert is yet assigned to your new metric. To create an alert in this template, proceed as follows (the descriptions of this and the next step are under Creating Alert Types for the New MAI Metrics):
Choose
. A customer alert creation wizard starts.Enter the general attributes of the new alert in the Overview
tab:
Attribute | Value |
---|---|
| Update: Queue Waiting Time Too Long |
|
|
|
|
| Do not change this entry. |
| Do not change this entry. |
| ZA_R3UPDATEQUEUETIME |
| Enter a description of your alert. |
Do not change the settings in the Messages
, Notifications
, Third-Party Components
and Auto-Reactions
tabs. These settings are then copied into the template.
In the Rule
tab, you specify how the alert color is determined if the alert has several metrics assigned to it. Do not change the value Worst Case Rule
.
Go to the second step (Assignments
) of the customer alert creation wizard. You can assign metrics to the alert. Choose the prviously created metrics Queue Waiting Time Update1
and Queue Waiting Time Update2
.
Note
Press the CTRL key while you select the metrics
Choose Finish
, to complete the creation of the alert.
Save your template.
You have created an alert for your new metric. The system generates a consolidation event with the same name as the alert, automatically. As the event is displayed independently of the status in technical monitoring, change the name. Proceed as follows:
Go to the Metrics, Events, Alert Hierarchy
tab.
Find the newly created alert Update: Queue Waiting Time Too Long
, and expand its subtree. The automatically created consolidation event is below the alert.
Choose the consolidation event of the alert, and name it Update: Queue Waiting Time
.
Save your template.
You have made the required changes to the customer template. To use the new metric and its alert in technical monitoring, assign the template to managed objects, and activate the assignment. This is described in Using Templates.
Go to SAP Solution Manager Configuration
step Define Scope
.
Select ABAP systems whose metrics you want to monitor, and go to the next step (Monitoring Setup
).
Choose Assign Templates
for all instances, and for the product SAP ABAP Basis
choose the previously created template Other CCMS Metrics
.
Activate the assignment with
.You have performed all steps required to integrate a CCMS metric into MAI; the metric is displayed in the Technical Monitoring
work center.
Start System Monitoring
of the ABAP systems to which you have assigned your template. The metric is in the technical instances, under .