SAP Monitoring allows you to monitor the availability and performance of SAP environment from a centralized web console. SAP monitor takes advantage of the SAP CCMS (Computer Center Management System) architecture to give insightful information about the SAP system along with fault management and reporting capabilities.
Prerequisites for monitoring SAP Server: SAP JavaConnector (JCo) should be present in Applications Manager's classpath. Learn more
Using the REST API to add a new SAP server monitor: Click here
Follow the steps given below to create an SAP server monitor in Applications Manager:
Note: While creating an SAP monitor, you need an SAP user profile with the following authorization objects: S_RFC, S_XMI_LOG and S_XMI_PROD which are minimum prerequisites for adding an SAP monitor.
The following parameters are monitored for SAP:
Parameter | Description |
---|---|
Monitor Information | |
Health | Specifies the health of the monitor based on its dependencies |
Type | Type of the Monitor |
Host Name | Specifies the host in which SAP is running |
Host OS | The Operating System of the host |
Last Polled at | The time at which last polling happened |
Next Polled at | The time at which the next polling is scheduled |
Availability | The current status of the SAP Monitor - whether it is up or down. |
System Information | |
CPU Utilization | Amount of CPU utilized by the SAP server (in percentage). |
Memory Utilization | Amount of memory utilized by the SAP server (in percentage). |
Disk Utilization | Amount of disk utilized by the SAP server (in percentage). |
Spool Utilization | Amount of spool work processes utilized by the SAP server (in percentage). |
Background Utilization | Amount of background work processes utilized by the SAP server (in percentage). |
Parameter | Description |
---|---|
Hit Ratio | Percentage of the database queries that were met from the buffer (hit rate) and did not have to be passed on to the database for different buffer types like Program, Repository, Table & GUI |
Directory Used | Percentage usage of the directory (number of entries) for different buffer types like Program, Repository, Table & GUI |
Space Used | Percentage usage of the buffer storage for different buffer types like Program, Repository, Table & GUI |
Swap | Swaps due to a full buffer per minute for different buffer types like Program, Repository, Table & GUI |
Parameter | Description |
---|---|
CPU Utilization | Average usage of the CPU in a host system |
Disk Utilization | Average usage of the disk in a host system |
Extended Memory | Utilization of the extended memory as a percentage. |
Private Memory | Utilization of the private memory as a percentage. |
Roll Area Usage | Usage of the roll area as a percentage |
Page In | Average number of page-ins per second; a page-in occurs if a process must access a data page that is not available in the main memory |
Page Out | Average number of page-outs per second (page-out occurs if a page is stored out of the main memory to make room for the pages required by other processes) |
Syslog Frequency | Number of messages per minute that appeared in the system log of an application server. |
Parameter | Description |
---|---|
Work Processes Overview | |
Total Work Processes | Number of total work processes. |
Running Work Processes | Number of running work processes. |
Waiting Work Processes | Number of waiting work processes. |
Stopped Work Processes | Number of stopped work processes. |
SAP Work Process Information | |
Server Name | Name of the server. |
No | The internal ID number of a process. Used to identify messages that belong to a work process in the system log. |
Type | The type of work process. Possible values are:
|
PID | Process ID of the work process (on the operating system). |
Status | Current status of the work process. Possible statuses are:
|
Reason | Reason displayed if a work process is in Hold status. |
Start | Indicates whether the process should be automatically restarted if a process ends prematurely. |
Error | Indicates how many times a work process has aborted since the instance was started. |
Sem | Indicates the number of the semaphore for which a work process is waiting. Normally, this field should be empty. |
CPU | Cumulative CPU time used by a work process since it was started. |
Time | Indicates the elapsed time used by a work process for the dialog step that it is currently being processed. |
Report | ABAP program or report that is currently being executed. |
User | User whose request is currently being processed |
Action | Action that is being performed by the program that is running. The actions that are displayed are those that are recorded by the SAP performance monitor. |
Table | Name of the table that is being accessed by the database. |
Parameter | Description |
---|---|
Background Processing | |
Background Utilization | Percentage of the background processing capacity currently utilized. |
System Wide Queue Length | Number of jobs that are ready to be executed, have start authorization and have no target server specified for which there are no free background work processes, averaged over all application servers with background work processes. |
System Wide Free Processes | Number of free background work processes |
Server Specific Queue Length | Number of released jobs that are explicitly to be executed on this application server, but for which there are no free background work processes |
Background work processes count | Number of background work processes on an application server |
Error count | Number of errors in background work processes since the monitoring segment was created (that is, since the application server was started) |
Error frequency | Number of errors in background work processes per minute |
Terminated on error count | Number of background work processes terminated after an error |
Running Background Work Processes | Number of jobs that are ready to be executed, have start authorization and have no target server specified for which there are no free background work processes, averaged over all application servers with background work processes. |
Waiting Background Work Processes | Number of free background work processes |
Stopped Background Work Processes | Number of released jobs that are explicitly to be executed on this application server, but for which there are no free background work processes |
Parameter | Description |
---|---|
Frontend Response Time | Average time that a user waits at the front end for the processing of his or her request |
Database Request Time | Average time for processing logical database requests |
Load And Generation Time | Average load and generation time of CUA objects |
Response Time | Average response time of the dialog service |
Network Time | Time used in the network during the first data transfer from the front end to the application server and during the last data transfer from the application server to the front end. |
Users Logged In | Number of users logged on |
Queue Time | Average time in the dispatcher wait queue |
Total Dialog Work Processes | Number of total dialog work processes. |
Running Dialog Work Processes | Number of running dialog work processes. |
Waiting Dialog Work Processes | Number of waiting dialog work processes. |
Stopped Dialog Work Processes | Number of stopped dialog work processes. |
Parameter | Description |
---|---|
Enqueue Requests | Number of lock requests |
Enqueue Request Rejects | Number of rejected lock requests |
Enqueue Requests Errors | Number of errors that occurred during lock requests |
Dequeue Requests | Number of release requests |
Dequeue Requests Errors | Number of errors that occurred when releasing locks |
Dequeue All Requests | Number of releases of all locks of an LUW |
CleanUp Requests | Number of releases of all locks of an application server |
Backup Requests | Number of update calls for which locks were forwarded to the update. |
Reporting Requests | Number of operations for reading the lock table. |
Owner Names Actual Utilization | Current number of lock owners in the lock table |
Granule Arguments Actual Utilization | Current number of different lock arguments in the lock table |
Granule Entries Actual Utilization | Current number of elementary locks in the lock table |
Update Queue Actual | Current number of open update requests with locks |
Recent Lock Time (per minute) | Time spent in the critical path of the lock table for lock operations (in seconds per minute) |
Recent Lock Wait Time (per minute) | Wait time of parallel processes before entering the critical path of the lock table (in seconds per minute) |
Recent Server Time (per minute) | Total time spent in the enqueue server (in seconds per minute) |
Enqueue Frequency | Enqueue operations (logical data locks) per minutes that are coming from another instance to the central instance |
Total Enqueue Work Processes | Number of total enqueue work processes. |
Running Enqueue Work Processes | Number of running enqueue work processes. |
Waiting Enqueue Work Processes | Number of waiting enqueue work processes. |
Stopped Enqueue Work Processes | Number of stopped enqueue work processes. |
Parameter | Description |
---|---|
Spool Utilization | Utilization of the spool work processes as a percentage |
Spool Work Processes Count | Number of spool work processes |
Spool Work Processes Errors | Number of errors in spool work processes |
Spool Work Processes Terminated | Number of spool work processes that terminated after errors |
Dispatcher Queue Utilization | Used area of the dispatcher queue as a percentage |
Request Queue Utilization | Used area of the spool request queue as a percentage |
Service Queue Priv | Used area of the spool request queue for processing in chronological order as a percentage |
Service Queue Pages | Number of pages in the spool request queue |
Device Cache Used | Used area of the entire device cache as a percentage |
Device Cache Fixed | Used area of the fixed device cache as a percentage |
Host Spool List Used | Used area of the host spool request list as a percentage |
Used Numbers | Amount of used numbers as a percentage |
Alerts | Shows all the alerts under System Errors tree node of SAP CCMS monitor [RZ 20]. When you set an alert to completed status, it is deleted from the active alerts that are shown in the Alert Monitor and the Alert Browser. |
Running Spool Work Processes | Number of running spool work processes. |
Waiting Spool Work Processes | Number of waiting spool work processes. |
The Update tab details have been split into two nodes: Performance Update 1 and Performance Update 2.
Parameter | Description |
---|---|
Total Update Work Processes | Total number of update work processes. |
Running Update Work Processes | Number of running update work processes. |
Waiting Update Work Processes | Number of waiting update work processes. |
Stopped Update Work Processes | Number of stopped update work processes. |
Performance U1 | |
Total Update Work Processes | Total number of Update 1 work processes. |
Running Update Work Processes | Total number of running Update 1 work processes. |
Waiting Update Work Processes | Total number of waiting Update 1 work processes. |
Stopped Update Work Processes | Total number of stopped Update 1 work processes. |
Response time | Average response time of Update 1. |
Utilization % | Utilization of Update 1 as a percentage. |
Performance U2 | |
Total Update Work Processes | Total number of Update 2 work processes. |
Running Update Work Processes | Total number of running Update 2 work processes. |
Waiting Update Work Processes | Total number of waiting Update 2 work processes. |
Stopped Update Work Processes | Total number of stopped Update 2 work processes. |
Response time | Average response time of Update 2. |
Utilization % | Utilization of Update 2 as a percentage. |
Parameter | Description |
---|---|
Date | The date at which the alerts were generated. |
Time | The time at which the alerts were generated. |
System | System ID of the SAP instance. |
Context | Name of the monitoring context to which the MTE belongs. |
Object Name | Name of an ABAP Dictionary Object. |
Module Name | Short name of the MTE. |
Severity | Severity of the alarm. |
Alarm Message | Displays the detailed information for the alert shown. |
In addition, you can also perform the following operations with respect to the alarms in SAP server monitor:
Parameter | Description |
---|---|
Job Name | The name of the background job monitored. |
Current Status | The current status of the background job. Possible Statuses are:
|
Last Run Status | The status of the background job during last execution. Possible Statuses are:
|
Last Run Date & Time | The date & time of the last executed background job. |
Runtime (Sec) | The runtime in seconds ( the difference between starttime and endtime) of the last executed background job. |
Delay(Sec) | The delay in seconds ( the difference between scheduled starttime and starttime) of the last executed background job. |
Age | Time since last execution of the background job in minutes. |
Note: Click the icon to view the logs of a terminated background job and it's history.
Parameter | Description |
---|---|
Lock Statistics | |
Shared Locks | Type of lock where several users (transactions) can access locked data at the same time in display mode. |
Optimistic Locks | Type of lock which initially behaves like shared locks and can be converted into exclusive locks. |
Exclusive Locks | Type of lock which protects the locked object against all types of locks from other transactions. |
Non Cumulative Locks | Type of lock which can be requested only once by the same transaction. |
Total locks | The total number of locks present. |
Lock Entries | |
User Name | Name of the user who set the lock. |
Timestamp | The timestamp in which the lock entry was created. |
Lock Argument | The Argument(key field) of the lock entry. |
Lock Mode | The type of the lock object. Lock types are: S (shared lock), E (exclusive lock), X (exclusive non-cumulative lock), O (optimistic lock) |
Table Name | The name of the table in which rows are locked. |
Host Name | Name of the host in which the lock is created. |
Transaction Code | The transaction code from where the transaction is called. |
Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system. Applications Manager monitors metrics pertaining to Queued RFCs (qRFC) and Transactional RFC (tRFC) like:
Parameter | Description |
---|---|
QOUT Scheduler (SMQS) | |
Client | The Logon Client. |
State | The status of the Scheduler at the moment when SMQS is executed. Possible states are: SYSFAIL, CPICERR, INACTIVE, WAITING, WAITCONN, STARTING, ACTIVE. |
Time | The time of last update. |
Group | The group to which this scheduler belongs. |
Host | The host in which this scheduler is running. |
QIN Scheduler (SMQR) | |
Client | The Logon Client. |
State | The status of the Scheduler. Possible states are: SYSFAIL, CPICERR, INACTIVE, RESOURCE LACK, WAITING, BATCH , ACTIVE,STARTING. |
Time | The time of last update. |
Group | The group to which this scheduler belongs. |
Host | The host in which this scheduler is running. |
QOUT Data (SMQ1) | |
Client | The Logon Client. |
Queue Name | The name of the queue. |
Destination | The target destination of the queue. |
State | The current state of the queue. Possible states are: SYSFAIL, CPICERR, STOP, SYSLOAD, VBERROR, READY, RUNNING, NOSEND, NOSENDS, WAITING, WAITSTOP, WAITUPDA, RETRY, ARETRY, ANORETRY, MODIFY, EXECUTED, AFINISH, FINISH. |
Message | The message while executing the queue. |
Time | The time of last update. |
QIN Data (SMQ2) | |
Client | The logon Client. |
Queue Name | The name of the queue. |
State | The current state of the queue. Possible States are:SYSFAIL, CPICERR, STOP, READY, RUNNING, WAITING, WAITSTOP, RETRY, ARETRY, ANORETRY, MODIFY, EXECUTED, NOEXEC, AFINISH, FINISH, SAVED. |
Message | The message while executing the queue. |
Time | The time of last update. |
Transactional RFC (SM58) | |
Transactional ID | The identifier of the Transaction. |
Functional Name | The name of the function that executed for transaction. |
Destination | The target destination where this function is executed. |
Caller | The user who called this transaction. |
State | The state of the transaction. Possible States are : CPICERR, SYSFAIL, CONFAIL, RECORDED, VBERROR, SYSLOAD, RETRY, ARETRY, ANORETRY, EXECUTED, MAILED, READ, VBRECORD, SENDED, DEBUG, VXRECORD |
Message | The message while executing the transaction. |
Time | The time of last update. |
Tcode | The Tcode from where this transaction is called. |
Data Retention: For Transactional RFC, only 2 hours of RAW data will be retained. After two hours the collected RAW data available in Applications Manager database will be deleted. This is because of the HUGE volume of transaction data available in SAP system. Applications Manager database will not scale the huge volume of transaction data.
Data Archiving: Data archiving of transaction data will not happen due to the following reasons.The alert history will be available but no reporting is possible for Transactional RFC.