Background Job Monitoring Monitor

Use

You can use the monitoring architecture to monitor selected jobs and to display problems as alerts (see Monitoring Jobs with the Alert Monitor). This job monitoring is deactivated by default; activation is described in Activating Monitoring of Jobs with the Alert Monitor.

After activation, the data is available in the context Background, Background Job Monitoring subtree. For the monitoring, it is useful to define your own monitor or to extend a monitor definition of your own to display the data. The monitor definition and the monitor produced from it are described here.

Prerequisites

You can define a rule-based or a static monitor to display data. For basic information about this, see Creating and Changing Monitors. For a rule-based monitor, the definition must contain a rule CCMS_GET_MTE_BY_CLASS with Job_Monitoring as the MTE class:

If you are using a static monitor, choose the context Background ® Background Job Monitoring for the desired system:

Features

With the definition above, the monitor created has the following structure. Here, the job SCHEDULED_JOB1 and all jobs whose names begin with JOB_EXAMPLE are to be monitored. A subtree is created for every name pattern for a monitored job (job chain):

The monitor contains the following monitoring tree elements (MTEs):

MTE Name (MTE Class)	Meaning
Details of Current Job (Job_Monitoring_Details)	Double click this MTE to obtain the following current information about the current job: · Name, number, and class of the job · Date and time scheduled, the last change to and release of the job, and user that performed each of these actions · Last planned start and the actual last start and stop of the job · Server, work process number, and process ID of the last run of the job · Status and target server of the job These values may differ from the values Delay and Runtime beow, as the current values are collected here, while Delay and Runtime are collected by the data collection method, which runs every five minutes.
Status (Job_Monitoring_Status)	Last entry in the job log for the job with the relevant name pattern: Name, number, status, and planned and actual execution time of the job. A job is reported in the job log if it has the status active, finished, or canceled. A red alert is generated if the job exceeds its scheduled start time, remains in the Ready status for a long time, or was canceled.
Log of Current Job (Job_Monitoring_Joblog)	In addition to possible error messages, this node displays the start, each step, and the end of each job that matches the relevant name pattern; logs for different jobs are separated by an empty line.
Runtime (Job_Monitoring_Runtime)	Runtime of the current job of a chain of periodic jobs. If the current job has not yet been started, the node is green and the value for the runtime is 0.
Delay (Job_Monitoring_Delay)	Delay of the current job of a chain of periodic jobs; if the planned start time of the current job has been exceeded and the job has not yet started, the node displays the difference between the measurement time point and the planned start time
Delay + Runtime (Job_Monitoring_dplusr)	Total of Delay and Runtime
History (Job_Monitoring_History)	Like the entries in the Status attribute (see above), however, not only the last entry, but a history of previous entries (choose the Display Details button (), to display the history) The entries also contain runtimes and delays. To improve clarity, these values are displayed in the following units: t £ 300 sec. : Displayed in seconds 300 sec. < style=""> Displayed in minutes t ³ 1 day: Displayed in days

Customizing Alert Generation

· Runtime, Delay and Delay + Runtime

Threshold values are already assigned to these performance attributes by default, so that an alert is generated as of a defined runtime or delay. To change the threshold value, select the desired performance attribute and choose Properties (see Changing Properties and Method Assignments). Ensure that you choose Edit ® Properties ® Use for individual MTE so that you do not change the threshold values for the other monitored jobs.

· History and Log of Current Job

By default, these log attributes always have the color green. However, you can also assign a yellow or red alert to particular messages of the attribute. To do this, choose Properties and specify the class and ID of the desired message on the Filter tab page.

To determine this data for a message of the log attribute, follow the procedure below:

i. Select the desired log attribute and choose the Display Details button ().

ii. The Monitoring Attributes - Detail Data screen appears. To do this, select any row from the list of messages and choose Current Display Variant ().

iii. The Change Layout screen appears. Ensure that the fields for message class (MsgKlasse) and the message ID (MsgId) are displayed, and accept the changes.

iv. The class and ID of the message are now displayed in the list.