The purpose of Job & Automation Monitoring, which is available as of SAP Focused Run 3.0 FP02, 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 of automation processes (for simplification called “jobs” in the later text) that run on the different platforms with a unified user experience using a common look-and-feel and handling pattern. It aims to replace the Job Monitoring application that supports the monitoring of ABAP jobs only. See a short introduction and comparison with Job Monitoring here.
The basic concept is to collect individual job execution data into the central monitoring application, to correlate it to the related job definition and evaluate every execution using historical data. The rating of the last execution is propagated to the job level and finally to the service level so that you can understand easily the current status of the jobs executed. 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 service to support a more detailed analysis, e.g. in order to stop a not ending execution or to restart a failed execution.
Job & Automation Monitoring shall help to understand the success of the automation processes, cross all involved cloud services and systems. In case of a SAP ABAP system it shall help you to monitor efficiently Standard Jobs, which are those jobs that are scheduled by the SAP S/4HANA technical job repository (see SAP Note 2190119) or in lower releases by the SM36 Standard Job framework.
It is planned to offer job analytics for the different monitored aspects (e.g. runtime and exception trend reporting) so that critical trends can be discovered and downtimes avoided.
Job & Automation Monitoring in SAP Focused Run collects data for these job types:
Job & Automation Monitoring in SAP Focused Run collects job or automation data for these products:
The Status Overview provides a summary regarding job execution for the systems in scope. It shows the number of systems and the number of automations ("jobs") with a rating of the latest executions with regards to their Execution Status, Application Status, Start Delay and Run Time. Finally, the number of alert situations is displayed, alerts for jobs that have been created, that are not yet confirmed.
The Application Overview provides a card based overview, with more details:
In the Alert Ticker you see the most recent Job & Automation Monitoring alerts for the services in scope. Please note that alerts that are currently rated green are not displayed and counted in the alert ticker. In contrast the Job & Automation Monitoring considers alerts as long as they are not confirmed. Consequently the alert number in the Status Overview section is typically higher than in the Alert Ticker.
You can get alerted, if a job has a red Executions Status, a red or yellow Application Status, if it's Delay or Run Time exceeds a threshold that you can set.
You can adjust the Alert Name in order to describe, what is monitored, for example, if you restrict via filter an alert to specific jobs or set specific thresholds. The alert Additional Key contains the NAME, the TYPE and the CONTEXT of the job. Consequently alerts are raised for the managed system, per distinct job name, job type (and client in case of ABAP). In the alert details you see the alert type and information on the latest job execution that raised the alert.
Flag and save the use case setting.
In order to get job data collected for a technical system, you need to select it into your scope and then you can configure for it the data collection. If you switch to "On", then by default for job type SAP ABAP job job execution data is collected from all clients. In the detail view you can restrict the clients and also collect further job types. Currently SAP BW Process Chain is offered.
Once job data is loaded from the managed system, you will see that all 4 aspects, i.e. Execution Status, Application Status, Start Delay and Run Time are rated. The rating is set automatically according to the Rating Rules, for which you can adjust the thresholds for Start Delay and Run Time. Please note that this change is applied only to your session, it is not (yet) possible to save the setting.
For SAP ABAP jobs in many cases the rating of the Application Status is grey. This is normal, if the job does not write any application log messages.
If none of the jobs is rated regarding the Application Status, the reason might be that in the managed ABAP system, SLG1 entries are not linked to ABAP job executions, as this needs to be configured in transaction CRIT. In the as depicted example below, all jobs in client 200 are linked to the application log entries that they write.
To configure alerting for specific jobs, expand the configuration pane and then access the system, for which you want to configure alerting.
Per system you can define alerts of category Critical Execution Status, Critical Application Status, Critical Runtime and Critical Delay. If you want alerts to be created only for certain jobs use the filters. In order to properly fill the values, check the corresponding information in the job monitoring application.
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 stop to get alerted, you can switch off the alert or delete the configuration.
In the Alert Settings section you can find and maintain the typical SAP Focused Run alert and notification settings:
Maintain in the alert resolution text, what shall be done in case of an alert. A default text is entered, when you create an new alert.
In SAP Focused Run Job & Automation Monitoring data is reorganized with a default rule that you cannot change. The rule is, that for every job at least the last 15 executions are kept and on top all failed executions for 3 days. Jobs that are deleted in the managed service, i.e. that are not scheduled any more, are flagged as deleted in SAP Focused Run and removed from the database after 2 weeks together with the related executions and schedules.
Note: If you have configured alerts, please ensure to confirm alerts as alerted job executions are not removed from the data base.