The purpose of Job Monitoring is to provide transparency about the current status of automation processes regarding execution status, application status, start delay and run time. It supports the monitoring jobs running on the different platforms with a unified user experience using a common look-and-feel and handling pattern.
The basic concept is to get all individual job executions pushed into the job monitoring application and to evaluate them using historical data. The determined ratings are aggregated to the job level and to the system / service level so that you can see the current overall status of all jobs. In case of issues with job executions, context-based navigation is offered from the aggregate to the individual job execution and finally a direct navigation to the corresponding job instance in the executing system / service for a more detailed analysis.
Job Monitoring shall help IT users and Business users to understand the success of the automation processes they are responsible for, across all involved cloud services and systems.
On top of showing the current status and indicate exceptional situations, it is planned to offer job analytics (measured values and Z-score trend reporting) for the different metrics in order to detect and avoid critical situations proactively.
Job monitoring in Cloud ALM for Operations is currently offered for SAP Application Jobs used in various products like
The monitoring overview provides a status overview per cloud service, to help understand the overall current status of the jobs, i.e. the status of the latest execution(s) with regards to the Execution Status, Application Status, Start Delay and Run Time. At present, the SAP S/4HANA Cloud service is supported, i.e. the app displays the application jobs executed in the registered SAP S/4HANA Cloud tenants and offers direct navigation into the job execution details of the corresponding SAP S/4HANA Cloud tenant.
The jobs view provides the list of jobs of all the services sorted by Execution Status rating in a descending order along with the rated information regarding Execution Status, Application Status, Start Delay, and Run Time. The summary rating of a job is the latest non-grey rating of the respective metric.
By clicking a job name, you can view the list of executions of the selected job sorted descending by planned start time.
By choosing the information icon next to each execution, you can view further details and navigate directly to job in the managed cloud service by clicking on the Run ID value.
Alerts can at the moment be raised, if jobs have a red Executions Status or a red or yellow Application Status. The Alert Name can freely be defined, and you can make use of the value that you defined for notification determination by Intelligent Event Processing. In the alert Object Details the name of the job is contained. In the alert list UI, you can filter for the content of the object details, i.e. the job name. Alerts are raised per job and contain all failed executions of a specific job. From the Run Id value, you can navigate to the corresponding job execution in the managed cloud service, just like from the job monitoring application.
Reporting on job run time trends, determining time periods with exceptional run times, delays and critical job statuses is planned to be offered in 2021.
For monitoring SAP S/4HANA based Application Jobs, there are no prerequisite steps to be done in SAP Cloud ALM, i.e. if you start to push job data as described below automatically an entry is created in the Landscape Management Service SAP Cloud ALM.
SAP S/4HANA based Application Jobs are used in various SAP products (like SAP Integrated Business Planning, SAP Marketing Cloud and SAP S/4 HANA Cloud, essentials edition). For this job type the data is pushed, i.e. in the managed S4HANA Cloud service you need to activate scenario SAP_COM_0527 'Application Monitoring Push Integration' and make sure to have 'Collect Job Monitoring' flagged.
As in SAP Cloud ALM all jobs are evaluated with a default rule no configuration for monitoring is needed. You can adjust the default rule, i.e. change the general threshold for the delay and duration metric rating determination.
In order to configure alerting for specific jobs, you need to have role Job Monitoring Administrator assigned. Expand the configuration pane and then access the service, for which you want to configure alerting.
Per service you can define alerts of category Critical Execution Status or Critical Application status.
In order to specify, which jobs should be considered for the alert you can specify job name, executing user and the name of the job executable. The filter conditions for the different parameters are connected with AND for the same parameter with OR. On saving, the alert is activated. If you want to deactivate but not yet delete an alert, switch it off.
Role Job Monitoring Consumer is sufficient adjust the rating of the Start Delay and Run Time metric in the job monitoring application. Below you see the default settings. Note, that the setting is not persisted, i.e. if you relaunch the application the default will be applied again.
In case you encounter problems configuring or using SAP Cloud Application Lifecycle Management, please report an incident using one of the following components:
Please select one of your SAP Cloud Platform Integration Systems when reporting the incident.