Job & Automation Monitoring

Scope & Content

Scope

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.

Content

Job & Automation Monitoring in SAP Focused Run collects data for these job types: 

  • SAP ABAP Jobs
  • SAP BW Process Chains

Supported Products

Job & Automation Monitoring in SAP Focused Run collects job or automation data for these products: 

  • SAP Business Suite

Features

Home Page

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:

  • Last execution had an exception - All Job Types provides information on the number of jobs, where the last execution had an issue in the different aspects.
  • Last execution had an exception - Standard Job provides the information for Standard Jobs
  • Open Job Alerts - All job types provides information on the alert numbers per alert type. 
  • Open Job Alerts -Standard Job provides the information for Standard Jobs. 

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.

Monitoring

  • You get for all systems in scope the monitored jobs listed and rated regarding Execution StatusApplication StatusStart Delay and Run Time. The rating reflects the rating of the respective aspect for the latest execution of the job. 
  • The list of jobs is sorted by Execution Status rating in a descending order. You can change the sorting and apply filters. 
  • You see in column Open Alerts the number of not yet confirmed alert situations and by clicking on the number you get the alert details listed in another screen
Drill-down to failed executions and job in remote system:
  • By clicking on a name, you can view the list of executions for the selected job sorted by planned start time.
  • By clicking on the arrow in the end of the line, you can view run details on the executed actions (e.g. reports and variants).

  • By clicking on the information icon next to each execution, you can view further details and navigate directly to the job in the managed system by clicking on the Run ID value.

Alerting

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. 

Use Cases

  •  You are responsible for ABAP Standard Jobs:
    • Configure to get alerted, if a job fails / cancels
    • Configure to get alerted, if a job stops to get executed  or runs less frequent than it should *
    • Configure to get alerted, if the run time of a job is longer than a fixed threshold
  •  You are responsible for a list of jobs:
    • Configure to get alerted, if a job fails / cancels
    • Configure to get alerted, if a job stops to get executed or runs less frequent than it should *
    • Configure to get alerted, if the run time of a job is longer than a fixed threshold
    • Configure to get alerted, if the job has application issues, e.g. writes errors or warnings into the ABAP application log
  •  You are responsible for the batch processing in one or more systems or for a list of jobs:
    • Understand, that no job shows a run time deterioration **
    • Understand, if that no job shows an increasing failure rate **
    • For critical jobs understand, if there are times, with long run times and / or high failure rate **

* possible as of SAP Focused Run 3.0 FP03 by defining one or more jobs as mandatory and configuring the (new) alert type "Missing execution of mandatory job"

** possible as of SAP Focused Run 3.0 FP03 via the (new) view "Analysis" and the (new) view "Trend Graphs")

Prerequisites

  • In managed ABAP system ST-PI 740 SP16 or SP17 + SAP note 3102288 is implemented (managed ABAP system needs to have SAP_BASIS 7.4 & above)
  • SDA version is at least 1.59 (for download see here)
  • In SAP Focused Run System the following SAP notes are applied: 
    • 3126422  - FRUN 3.0 FP02 Job Monitoring back-end corrections
    • 3126368  - FRUN 3.0 FP02 Job Monitoring UI corrections    

Setup

Activation of Job & Automation Monitoring Use Case

Flag and save the use case setting.

Configuration of Data Collection in Job & Automation Monitoring Application

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.

Configuration

Monitoring

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. To ensure that application log messages that are written during batch execution of a program are linked to the job execution you need to do following configuration:

  1. call transaction CRIT
  2. add "Auto-linking Applog-Handles for jobs"
  3. activate the profile

In below example the linking is restricted to jobs executed in client 200. Please note, that with "Option" [=] the value * will be interpreted as *. For patterns make sure to use "Option" [x].

Alerting

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 StatusCritical Application StatusCritical 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.

 

Alert Types

  • Critical Execution Status: Alert is raised, if a job fails to finish successfully, e.g. in case of an ABAP job cancels.
  • Critical Application Status: Alert is raised, if a job writes applications errors or warnings, e.g. in case of an ABAP job SLG1 (Application Log) errors or warnings (remember: For ABAP jobs you need to maintain CRIT as explained above). You can restrict the alert to "red application status rating". By doing so, alert will be raised for ABAP jobs in case of Application Log errors, but not for warnings.
  • Critical Runtime: Alert is raised, if a job execution runs longer than the defined threshold, i.e. "end time - start time > threshold value".
  • Critical Delay: Alert is raised, if a job execution is delayed by more time than the defined threshold, i.e. "start time - planned start time > threshold value". Alert is not raised, if the planned start time falls into a planned downtime.

Alert Filters

For the filter values you can use the conditions "is", "is not" or "contains". Patterns are not supported at the moment.
  • ABAP client: Filter is offered in case of Application Server ABAP. Use the filter, if you want to restrict the alert to specific clients (in the Additional Key of the alert, the client is the value behind the CONTEXT field)
  • Job / Automation Executable Name: Use the filter, if you want to restrict the alert, e.g. in case of ABAP jobs to those that execute a specific report and variant. Check in the monitoring application for the value, that that you need to enter.
  • Job / Automation Execution User: Use the filter, if you want to restrict the alert to jobs that are executed by a specific user. Check in the monitoring application for the value, that that you need to enter.
  • Job / Automation Name: Use the filter, if you want to restrict the alert to jobs that have a specific name. Check in the monitoring application for the value, that that you need to enter.
  • Job Type: Use the filter, if you want to restrict the alert to jobs of a specific type (at the moment "SAP ABAP Job" or "SAP BW Process Chain"). Use the F4 help.
  • Standard Job: Use the filter, if you want to restrict the alert to jobs that are considered a system or standard jobs. In case of an ABAP system, the jobs, that are scheduled by the job repository. Use the F4 help.

Alert Settings

In the Alert Settings section you can find and maintain the typical SAP Focused Run alert and notification settings:

  • Alert Severity: Set to a high value, if you want to get in the alert inbox a high priority assigned to the alert. Please note, that the current rating of the alert influences its priority, for example
    • if Alert Severity is set to 0 - Low , and Current Rating for instance is Red then - Alert Priority is set to Medium.
    • if Severity is 0 - Low, and Current rating is Green then- Alert Priority is set to Low.
  • Alert Per: Set the value to Job / Automation Execution, if you want to get notified for every execution of a job that raises the alert. By default you will get notified only for the first alert.
  • Automatic Alert Confirmation: If the flag is set, an alert gets confirmed automatically, if a succeeding execution of the same job did not raise the alert.
  • Notification Variant: Enter the variant that shall be used when triggering a notification. If no value is entered, the global variant will be used, if that is maintained.
  • Outbound Variant: Enter the variant that shall be used when triggering an external incident system. If no value is entered, the global variant will be used, if that is maintained.

Alert Resolution

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.

Housekeeping

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.

Troubleshooting

Issue: After switching on data collection for a technical system of Type Application Server ABAP the status of data collection stays in "in progress" for more than 15 minutes or switches to "failed”. 

Background: By switching on data collection for a managed system you have implicitly created a filter for job type SAP ABAP Job and will collect job data from all clients or you have explicitly created filters, e.g. if you want to collect ABAP jobs only from certain clients or collect BW process chains. 

Troubleshooting: Before opening a message please check

  1. in SM37, if the job SAP_FRN_JAM_DATA_COLLECTION is scheduled as described in the master guide
  2. in Agent Administration for the technical system, 
  • if the version of the agent is >= 1.59 (with 1.60 onwards, the “Data Collection failed” status is reflected in SAP Focused Run)
  • if (in Configuration Information) the following files are received from SAP Focused Run for creation or deletion of threads based on activation or deactivation of filters in monitoring configuration
    • com.sap.solman.agent.jobmon.housekeeping
    • com.sap.solman.agent.jobmon.metadata
    • com.sap.solman.agent.jobmon.runtime
  • if (via Agent Internals in tab Collector Framework) the following threads have been created
    • in case of ABAP job monitoring
      • jobmonhousekeeping [<<FRUN SID>>.JOB_ABAP_HOUSEKEEP_OP_<<host>>_<<LMDB ID of managed system>>] Period [86400 S]
      • jobruntime [<<FRUN SID>>.JOB_ABAP_RUNTIME_OP_<<host>>_<<configuration ID of filter>>] Period [300 S]
      • metadata [<<FRUN SID>>.JOB_ABAP_METADATA_OP_<<host>>_<<LMDB ID of managed system>>] Period [300 S]
    • in case of BW Process Chain monitoring
      • jobmonhousekeeping [<<FRUN SID>>.JOB_BW_HOUSEKEEP_OP_<<host>>_<<LMDB ID of managed system>>] Period [86400 S]
      • jobruntime [<<FRUN SID>>.JOB_BW_RUNTIME_OP_<<host>>_<<configuration ID of filter>>] Period [300 S]
      • metadata [<<FRUN SID>>.JOB_BW_METADATA_OP_<<host>>_<<LMDB ID of managed system>>] Period [300 S]