The monitoring architecture contains various data suppliers that deliver the data for the monitoring of your IT landscape. In this way, the monitoring architecture is, for example, provided with values for the following areas:
· Database
· Background processing
· Communication
· Operating system
· Spool
· Dialog system
· System log
· Memory management
You can find the corresponding data, especially in the monitors of the SAP CCMS Monitor Templates monitor set. There are also data suppliers for special monitoring functions that are constantly further developed and extended.
A selection of the most important special monitoring functions that are available to you in the monitoring architecture is listed below:
· Monitoring Log Files with CCMS Agents
Every CCMS agent can search log files for any text pattern and forward found patterns to the monitoring architecture as alerts of any criticality. The results are displayed in the Logfile Monitoring monitor.
· Monitoring Selected Processes with SAPOSCOL
You can monitor the availability of any processes using the operating system collector SAPOSCOL. These are displayed in the Monitored Processes subtree of the Operating System monitor. The monitor displays the number of running processes and the CPU and memory usage for each name pattern, broken down by different users.
· Availability Monitoring with CCMSPING
With availability monitoring, you can monitor the availability of remote SAP systems and their application servers from a central SAP system.
· Self-Monitoring of the Alert Monitors
The monitoring architecture also contains a detailed self-check with which you can monitor the status of the monitoring architecture, the Alert Monitor, and the methods. For this self-monitoring, there is a monitor in the SAP CCMS Technical Expert Monitors monitor set called CCMS Selfmonitoring.
· Monitoring Response Times of Transactions or Clients
You can use this monitor to monitor the response times of individual transactions or clients, which enables you to check Service Level Agreements.
· Monitoring qRFC and tRFC Calls
These calls are variants of the Remote Function Call. A transactional RFC is executed only once in the target system, and either all or no calls of a Logical Unit of Work (LUW) are performed; queued RFC also guarantees the chronological processing of RFCs
· Monitoring Database Tables with the Alert Monitor
You can search selected database tables for certain content and have an alert displayed if the content is found. When doing so, you can use any comparison operations for numerical content of the monitored table column, which must be fulfilled for an alert to be reported.