eG Monitoring
 

Measures reported by AsAbapBGJobTest

This test monitors the distribution of background jobs according to the job status. Apart from montoring the overall job execution, this test helps to debug issues that occurred due to long running jobs, aborted jobs and jobs with high start delays.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
numActive Indicates the number of jobs of this priority class that are currently active. Number  
numReady Indicates the number of jobs of this priority class that are waiting for execution by the background work processes. Number A low value is desired for this measure. If there is a sudden/gradual increase in the value of this measure, then it indicates that the background work processes are insufficient to execute the jobs. Therefore, administrators may need to check the number of background work processes and provision them accordingly.
numLongRunning Indicates the number of jobs of this priority class that have been running for a duration longer than than the cutoff time specified in the LONGRUNNINGCUTOFF parameter. Number Generally, the jobs may be classified as a long running job when the job is stuck during execution and loops the execution several times without completion. A high value for this measure is a cause of concern as long running jobs consume too much of resources thus leading to the performance degradation of the SAP instance.

The detailed diagnosis of this measure if enabled, lists the name of the job, job count, report name, user details, timestamps, duration etc.,

numNew Indicates the number of jobs of this priority class that were started during the last measurement period. Number A gradual decrease in the value of this measure is a cause of concecrn. Administrators may need to check the number of backgroung processes that are free and provision them according so that the background processes can execute the jobs continuously.
numDelayed Indicates the number of jobs of this priority class that started with a delay time greater than the time specified against the HIGHDELAYCUTOFF parameter while configuring the test. Number A low value is desired for this measure.

The jobs may be started with a delay due to various reasons such as unavailable background work processes, scheduling issues between the originating server and target server, other dependencies etc., This measure helps detect such issues by providing the details of these jobs including the exact start delay in milliseconds.

numAborted Indicates the number of jobs of this priority class that were cancelled/aborted during the last measurement period. Number Jobs may be abruptly terminated either manually or due to underlying program errors. Program errors could in turn be due to various issues such as authentication, file access, dead locks, updates, tablespace, memory, programming errors, dependencies etc., Therefore, a sudden/gradual increase in the value is a cause of concern which indicates severe performance degradation fo the target server.

The detailed diagnosis of this measure if enabled, provides details and logs for the aborted/cancelled jobs in order to facilitate troubleshooting.

AvgDelay Indicates the average time delay experienced in starting the jobs of this priority class. Milliseconds Comparing the value of this measure across the priority classes helps you identify the class in which the jobs experienced the maximum start delay.
numFinished Indicates the number of jobs of this priority class that completed execution during the last measurement period. Number A high value is desired for this measure.

This measure is a good indicator of the performance of the background processing system. The higher the value of this measure the greater is the performace of the targe server.