SAP monitor 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.
Availability tab, gives the Availability history for the past 24 hours or 30
days. Performance tab gives the Health Status and events for the past 24 hours
or 30 days. List view enables you to perform bulk
admin configurations.
|
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.
|
| 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 |
| Buffer |
| 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 |
| Dialog |
| 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 |
| Enqueue |
| 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 |
| Operating System |
| 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. |
| Spool system Details |
| 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 |
| 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.
|
| Background Jobs |
| Job Name |
The name of the background job monitored. |
| Current Status |
The current status of the background job.
Possible Statuses are:
- No Released Job Exists,
- Scheduled,
- Released,
- Active.
|
| Last Run Status |
The status of the background job during last execution.
Possible Statuses are:
- Finished,
- Terminated,
- - (No Status If it is executed for first time)
|
| Last Run Date & Time |
The date & time of the last executed background job. |
| Runtime (Sec) |
The runtime in seconds (difference between starttime and endtime) of the last executed background job. |
| Delay(Sec) |
The delay in seconds (difference between scheduled starttime and starttime) of the last executed background job. |
| Age |
Time since last execution of the background job in minutes.
|
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. |
icon to view the l