This is one stop global knowledge base where you can learn about all the products, solutions and support features.
The following monitoring content is for Integration Hub for Life Sciences
| Category | Type | Description |
|---|---|---|
| Replication Messages | Messages | Monitors replication messages in Integration Hub for Life Sciences |
To perform the necessary setup steps in the Integration Hub for Life Sciences, please refer to:
To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.
Below you find category-specific information for the monitoring categories available for Integration Hub for Life Sciences.
Please note:
Available Filters
| Filters for Data Collection | Filters for Events |
|---|---|
|
|
The following monitoring content is available for SAP Data Intelligence.
| Category | Type | Description |
|---|---|---|
| SAP Data Intelligence Messages | Messages | Messages send to and from SAP Data Intelligence |
To perform the necessary setup steps in the SAP Data Intelligence, please refer to:
To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.
Below you find category-specific information for the monitoring categories available for SAP Data Intelligence.
Please note:
Available Filters
| Filters for Data Collection | Filters for Events |
|---|---|
|
|
This portal page describes the monitoring setup for SAP Business ByDesign tenants.
The following monitoring content is available for SAP Business ByDesign:
| Category | Type | Description |
|---|---|---|
| SAP Business ByDesign Messages | Messages | Monitors messages sent from and to SAP Business ByDesign |
To perform the necessary setup steps in the SAP Business ByDesign, please refer to:
To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.
Below you find category-specific information for the monitoring categories available for SAP Business ByDesign.
Please note:
Available Filters
| Filters for Data Collection | Filters for Events |
|---|---|
|
Which filter values make sense for SAP Business ByDesign messages depends on the message direction.
INCOMING Messages
OUTGOING Messages
|
The following monitoring content is available for SAP Omnichannel Promotion Pricing
| Category | Type | Description |
|---|---|---|
| Upload Messages | Messages | Monitors uploaded messages in SAP Omnichannel Promotion Pricing |
To perform the necessary setup steps in the SAP Omnichannel Promotion Pricing, please refer to:
To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.
Below you find category-specific information for the monitoring categories available for SAP Omnichannel Promotion Pricing.
Please note:
Available Filters
| Filters for Data Collection | Filters for Events |
|---|---|
|
|
The purpose of Job & Automation 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 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.
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 IT and Business users to understand the success of the automation processes they are responsible for, cross all involved cloud services and systems.
On top of showing the current status and indicate exceptional situations, job analytics is offered 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 Cloud ALM collects data for these job types:
Job & Automation Monitoring in SAP Cloud ALM collects data for these solutions and products.
The Overview provides a summary status regarding job execution for the services in scope . It shows the status of the latest execution of every job with regards to the Execution Status , Application Status and Run Time . On top it displays the number of alert situations, i.e. jobs for which an alert had been created, that is not yet confirmed.
Clicking on card Automations with Technical Issues you are navigated to the list of jobs sorted by Execution Status. If you click on Automations with Application Issues or Automations with Performance Issues you are forwarded to the same list, sorted accordingly. On clicking on Automations with Open Alerts you are navigated to the list of open alerts.
If you directly navigate to the Monitoring view, then you get a status summary per cloud service , i.e. the status of the latest execution of every job with regards to the Execution Status , Application Status , Start Delay and Run Time . On top you see the number of monitored jobs and the number of alert situations.
By clicking on the Service Name, you are navigated to the list of jobs for a service sorted by Execution Status rating in a descending order. You see also ratings regarding Application Status , Start Delay , and Run Time . The summary rating of a job is the latest non-grey rating of the respective aspect. If you click on any of the rating icons, you are navigated to the list sorted by the corresponding aspect.
By clicking on a name , you can view the list of executions of the selected job sorted by planned start time.
By clicking on the information icon next to each execution, you can view further details and navigate directly to the job in the managed cloud service or on-premise system* by clicking on the Run ID value .
*Note: If you use a SAP Web Dispatcher please maintain the URL of the Web Dispatcher as Logon URL for the respective System in SAP Cloud ALM Landscape Management .
In Monitoring in the job list view you can filter the list for specific jobs and have the option to define this list as favorite. After you have created the favorite by pressing the * icon, go to the home page and set a speaking title and subtitle (via the star icon) for the card.
From the favorite card you can forward navigate to monitoring, namely to the list of jobs that you have defined as favorite.
Use the Analysis view to identify those jobs that have the longest response times and highest number of exceptions. A trend icon indicates, if the failure rate or response time is up or down in the time frame selected taking the mid point of the time frame as comparison point.
For any job it offers aggregated information on total and average run time, number of executions and number of failed executions (regarding
Execution Status
or
Application Status
) and the resulting failure rate. By clicking on the arrow at the end of every line, you can drill down into various trend charts for the metrics.
Use the Exceptions view to check for exceptions of the services and systems in scope.
To get exception data collected in general please follow the instructions provided in Integration & Exception Monitoring. In case of issue with the view, please report it via component.
To get exception data collected related job exceptions, no additional configuration is needed as those are collected together with the job execution data. Currently the following job types are supported:
On click on the rating icon you are forward navigated to the list of exceptions related to the job execution.
*Prerequisite: ST-PI 7.40 SP20 or higher is implemented in the managed on-premise system and in /n/sdf/alm_setup use case Exception Monitoring is activated.
Use the Alerting view to check the job execution related alerts for the services in scope. You can configure to get alerted, if a job has a red or yellow Executions Status , a red or yellow Application Status, if its Run Time or Start Delay exceeds a defined threshold.
As you can adjust the Alert Name you can indicate what you have configured, e.g. the filters used. 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 alert type 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 execution popup in the monitoring application.
Please note, that a downstream action (like email) is triggered when there is a change in the event rating (green to yellow / red, yellow to red / green or red to yellow / green). This means also, that no new notification is sent on consecutive failures of the same job as the rating does not change.
Below we list the most important use cases that Job & Automation Monitoring offers:
For more details on prerequisites, setup, housekeeping, and customer support, please check the Job & Automation Monitoring - Setup & Configuration page.
There are no prerequisite steps to be done in SAP Cloud ALM. You need to have the role / authorization for Job Monitoring in SAP Cloud ALM, and you need to configure in your SAP cloud service(s) the push of job execution data as described under "Setup" below. This initial one-time activity needs to be done in every monitored service.
* 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:
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].
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 case of the ABAP job scheduler there is no job definition with a unique ID. When scheduling a job the user defines what shall be executed, gives a job name and on save this entity gets a run ID. The job name does not need to be unique as together with the run ID it is unique for the ABAP system. At execution of the job the next occurrence is determined, and the job data is copied to the next due date and gets a new run id value.
To be able to group the executions of a job for Job & Automation Monitoring a stable ID is formed by the data collector as a hash value:
|
ID |
Hash of |
|
JobId |
jobname + client + number of steps + job metadata[(step no + program + variant)] |
If a job constantly changes its name (e.g. job name contains a time stamp), the formed JobId hash value is not stable, which does allow to group executions under one JobID. To enable the grouping for such a case, the JobId hash value is formed without the job name and on the monitoring UI, such a situation is indicated as follows:
In such a case, please give the job a name that represents all related executions (by pressing the pencil icon).
Note: Several ABAP jobs that have changing names and that execute the same (i.e. client + number of steps + job metadata[(step no + program + variant)] are identical), cannot be distinguished by the monitoring application.
To
configure events for 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 events of category
If you want events to be raised only for certain jobs you can make use of the filter options and specify the job name ("Job / Automation Name"), what is being executed ("Job / Automation Executable Name") or who is executing the executable ("Job / Automation Execution User"). The filter conditions for the different parameters are connected with AND for the same parameter with OR.
The filter options offered are "Is", "Is not" and "Contains". The entered value is interpreted as a string, if for example you want to get alerted
To get alerted, make sure to switch on Create Alert and save. If you want to stop to get alerted, you can switch off the Event Action , or deactivate or delete the event in the list of events. Note that events are not raised for services, if those are in Maintenance or Disruption state (maintained in Business Service Management).
In order to send notifications for alerts to an email address
In SAP Cloud ALM Job & Automation Monitoring data reorganization is as follows:
Note: If you have configured alerts, please ensure to confirm them. To avoid data growth only the last 100 alerted executions are kept.
Be aware that SAP provides you in fair usage concept 8 GB HANA memory per month. If you extend the given memory you might need to subscribe additional memory blocks with our BTP service SAP Cloud ALM memory extension.
If the "Type" of a job or automation is missing, the reason is that run information exists without definition data.
In case of ABAP jobs, if the "Type" is missing for a small part of the jobs only (e.g. 1%), this could be a temporary issue, that disappears after one day as then resending is done. If the issue persists then the reason could be a bug in the data collector.
In SM37 all jobs are displayed, whereas in the monitoring application jobs that execute report RSPROCESS are not displayed. The reason is, that those jobs are elements of BW Process Chains. They are displayed as executables of the related BW Process Chain (job type SAP BW Process Chain ).
With note 3102288 (version 31) parent PPF jobs are collected, but not the child jobs that execute reports RBANK_PROC_START or RBANK_PROC_END. Those child jobs are consequently invisible in the monitoring application. The reason for not collecting their execution data is, that the parent job runs until all child jobs have finished and if any of the child jobs fails, the parent job has a message in its job log. If the collector (as of ST-PI 7.4 SP20) finds such messages, it rates the parent job yellow.
Configuration to pause and restart data collection is offered from Job & Automation Monitoring, but depends on the availability of the implementation in the managed system or service. For ABAP based systems or services the availability is as follows:
Note, that if the switch is disabled the status is determined based availability of job execution data from managed service (i.e. green, if job data received in the last 30 days).
Please check, if the prerequisite for exceptions to be collected for ABAP jobs is fulfilled:
A downstream action (like email) is triggered when there is a change in the event rating (green to yellow / red, yellow to red / green or red to yellow / green). This means also, that no new notification is sent on consecutive failures of a job as the rating does not change.
Please note, that a downstream action (like email) is triggered when there is a change in the event rating (green to yellow / red, yellow to red / green or red to yellow / green). This means also, that a new notification is sent on a "successful execution" after a "failed execution" as the rating did change.
Issue: In the Additional Alert Key we see job name FRN_ARP_0000001242. However, this job does not exist. The actual job names, that we see in SM37 are:
Answer: As explained in the Configuration section under Option to Set Name of Job with Changing Name : In case of the ABAP job scheduler there is no job definition with a unique ID. To be able to group the executions of a job for Job & Automation Monitoring a stable ID is formed by the data collector as a hash value that contains the job name. If a job constantly changes its name (e.g. job name contains a time stamp), the formed JobId hash value is not stable, which does allow to group executions under one JobId. To enable the grouping for such a case, the JobId hash value is formed without the job name and on the monitoring UI you have the option to give to such a job a name that represents the group of jobs. It is this name, that will be used at alert creation.
Still forward navigation from the alert details via URL to the job in the managed ABAP system is supported.
In case you encounter problems using or setting up Job & Automation Monitoring in SAP Cloud ALM, please report an incident using the following component:
Please select your SAP Cloud ALM tenant when reporting the incident.