Displaying the Availability Monitoring with
the GRMG in the Alert Monitor
Use
Use the Alert Monitor (transaction RZ20) to display availability data in the central monitoring system for components that are monitored with the GRMG.
Prerequisites
You have performed the customizing of the GRMG monitoring.
Activities
To display the desired data, follow the procedure below:
1. Choose CCMS →Control/Monitoring → Alert Monitor, or call transaction RZ20.
2. Open the monitor set and the monitor that contains the desired data. If you cannot find the required monitor, note the following points:
¡ You can use the global monitor Availability and Performance Overview of the monitor set SAP CCMS Monitor Templates in every case. The GRMG scenarios are in the subtree GRMG-Tested Availability (Web Components).
¡ In the monitor set for the application for which you are monitoring the availability with the GRMG, there is a monitor that contains a subtree with availability data. You can usually find this information in a subtree with the name Heartbeat. For more information, see the documentation for the application.
§ For availability information for monitored J2EE Engines, see Heartbeat monitor in the monitor set SAP J2EE Monitor Templates.
§ For availability information about monitored Java components of the Exchange Infrastructure, see the subtree Java Components → Heartbeats in the monitor Exchange Infrastructure of the SAP CCMS Monitor Templates monitor set.
¡ Monitor definitions are delivered with upgrades and Support Packages. Therefore, if you cannot find the desired monitor set or the desired monitor in your central monitoring system, ensure that the most recent Support Packages have been installed in the system.
¡ You can also download the required monitor definitions. For example, to find the newest CRM monitors in the SAP Service Marketplace, call the Quick Link crm-inst (http://service.sap.com/crm-inst) and follow the path SAP CRM 4.0 → CRM 4.0 Monitors → CRM Monitor Definitions. You can also search for relevant SAP Notes.
¡ You can also define a suitable monitor yourself, which contains exactly the data that your require (see Creating a Rule-Based GRMG Monitor).
Features
Once you have opened the required monitor, the system displays a subtree with the following structure:
The subtree contains the following monitoring Tree elements (MTEs); the names of the relevant nodes are determined by the values of certain tags in the associated Customizing file (indicated by angle brackets in the following table).
In this Example |
Naming Convention |
Description |
BE6 auf Host P3753 (J2EE) |
<scendesc> |
Root node of the subtree with the name of the GRMG scenario; this is usually the name of the monitored application |
Self-Monitoring: Scenario J2EE_630 001 |
Self-Monitoring: Scenario |
Subtree for the self-monitoring of the scenario; the subtree shows whether the scenario was successfully executed, that is, whether it was possible to check the availability (irrespective of the result) |
Run Status: BE6 auf Host P3753 (J2EE) |
Run Status: |
Monitoring object with the results of the self-monitoring |
|
Scenario executed |
Availability of the scenario as a percentage, by default averaged over the last 15 minutes |
|
Run Status/ Error Messages |
Status and error
messages of the scenario; to display the messages in the Alert Monitor, choose
the |
Session round trip time: J2EE_630 001 |
Session round trip time: |
Monitoring object with the duration of the availability monitoring
This subtree is only created if the property GET_RUN_TIME is set (see Measuring the Runtime of Availability Monitoring with the GRMG) |
|
Session Round-Trip Time |
Runtime from the GRMG application being called to the return of the result to the GRMG infrastructure; the time includes the network time for the request in addition to the processing time in the GRMG application (or in the Web server in the case of GRMG Lite scenarios) |
Test EJB container |
<compdesc> |
A component subtree is displayed for each monitored component of the scenario; the name is determined by the compdesc element of the Customizing file |
EJB Host3753 |
<compname> <comphost> |
A host subtree is displayed for each instance of a monitored component that is running on a different host; the host name is returned in the element comphost of the GRMG response; the technical name of the component is added to the host name as a prefix |
EBJ Host3753 001 |
<compname> <comphost> <compinst> |
An instance subtree is displayed for each instance of a monitored component on a host; the sequence number of the instance is returned in the element compinst of the GRMG response; this number is added to the technical name of the component and the host name as a prefix |
|
Availability |
Availability as a percentage, by default averaged over the last 15 minutes |
|
Status |
Log attribute with
status messages that are returned by the GRMG application using the GRMG
response; to display the messages in the alert monitor, choose |
If a monitored component is not functioning correctly, corresponding messages are returned in the Status log attribute. Note the difference to scenario errors, where the GRMG monitoring itself is not functioning correctly. A scenario error does not necessarily mean that the monitored component is not available.
If scenario errors occur, the subtree is no longer supplied with availability values, and a Heartbeat Alert is therefore triggered. Scenario errors are also displayed in the subtree Self-Monitoring: Scenario…. If the scenario has never functioned correctly, the scenario subtree is not generated, and you can only see the errors in Self-Monitoring: Scenario.... (see also GRMG Selfmonitoring Monitor).
Monitoring with the
Generic Request and Message Generator start page