You need to have the role / authorization for Job Monitoring in SAP Cloud ALM, and you need to configure your SAP cloud service(s) to push job execution data. This initial one-time activity needs to be done in every monitored service as described in the next chapter.
SAP S/4HANA based Application Jobs are used in various SAP products (like SAP Integrated Business Planning, SAP Marketing Cloud and SAP S/4HANA Cloud, essentials edition). To execute data of such jobs pushed to SAP Cloud ALM, you need to activate scenario SAP_COM_0527 'Application Monitoring Push Integration' and make sure to have 'Collect Job Monitoring' flagged.
SAP Intelligent Robotic Process Automation Jobs data is pushed after doing some configuration steps in your iRPA tenant as described here in SAP Help.
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, Critical Application Status, Critical Runtime and Critical Delay. If you want alerts to be created only for certain jobs you can specify job name, executing user and the name of what is being executed. 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 Monitoring UI jobs are evaluated with a default Rating Rule that you can adjust, if you have role Job Monitoring Consumer. Please note, that the setting is not persisted, i.e. if you relaunch the application the default will be applied again. Below you see the default settings.
In SAP Cloud ALM 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 Cloud ALM 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.
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.