Week 2: Monitoring and Alerting Unit 1: Business Process ...

Week 2: Monitoring and Alerting

Unit 1: Business Process Monitoring

2PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Business process monitoring

Overview

In this unit, you will learn about:

▪ Basic concepts of business process monitoring

▪ How to use business process monitoring

▪ How to configure business process monitoring



Why do we need a central business process monitoring?

Customer solution landscape is subject to

transformation:

▪ Transformation from a monolithic to a

multi-service landscape

▪ Increased complexity to find and

analyze issues in a distributed

environment

▪ Increased need to consider business

processes end-to-end

BPMON’s objective is to ensure business

continuity:

▪ Find and analyze operational business

exceptions

▪ Resolve critical operational business

exceptions

▪ Provide transparency on process

performance

SAP ERPSAP CRM

Lead-to-Cash

Create

Order

Create

Invoices

Fulfill

Order

Collect

Cash

Sell

Product

Market

Product

SAP S/4HANA

SAP Service

Cloud

SAP Customer

Data Cloud

SAP Marketing

Cloud

Lead-to-Cash

Create

Order

Create

Invoices

Fulfill

Order

Collect

Cash

Sell

Product

Market

Product

SAP Business Technology Platform

SAP S/4HANA

SAP Sales Cloud

SAP Commerce

Cloud

SAP S/4HANA

SAP Subscription

Billing

SAP Global

Track and Trace

SAP S/4HANA

SAP Commerce

Cloud

SAP Subscription

Billing

SAP Commerce

Cloud

SAP Subscription

Billing



Objectives of business process monitoring

KPI 1

Customer Landscape

(Cloud and On-Premise)

Business Processes of the Intelligent Suite

KPI 2 KPI n

Visualize process performance and disruptions

Identify business disruptions and exceptions

Business

Process

Monitoring

▪ Provides transparency on end-to-end

business processes within a distributed

and hybrid solution landscape

▪ Monitors processes’ health and detects

anomalies during process execution,

including drill down in business

documents

▪ Alerts users directly on process

disruptions, including automated

problem resolution

▪ Ensures business continuity to increase

business process execution quality and

performance

▪ Delivers predefined process content,

including auto-discovery of relevant

business process KPIs to be switched on


Global / Local

Process Manager

(LoB Management

/ Quality Lead)

Operational

Responsible / Executer

(LoB Operation)

Global / Local

Application Owner

(IT Operation)

I need to monitor operations of my

solutions:

▪ Overview of critical technical

deviations and affected processes

▪ Collaborate on assigned tasks for

critical exceptions

I need to monitor my E2E process:

▪ Monitor E2E process performance

▪ Understand critical business process deviations

▪ Receive automatic alerts in case performance

thresholds are in danger or violated

▪ Collaborate on created and assigned tasks for

critical exceptions

▪ Deep-dive into deviations to analyze root

causes

▪ Understand past, current, and predicted

process performance along multiple

dimensions

I need to monitor my operations:

▪ Monitor operative process performance

▪ See critical process deviations

▪ Check status of a specific document type (e.g.

open sales orders)

▪ Receive automatic alerts in case performance

thresholds are in danger or violated

▪ Collaborate on assigned tasks for critical

exceptions


Key personas and use cases


Five KPI categories provided:

▪ Throughput figures measure the average number of business

documents, line items, or schedule lines processed within a certain

time frame e.g. “Sales Documents Created”

▪ Backlog figures measure the number of business documents, line

items, or schedule lines not completely processed until an expected

date, in other words, the business transaction is overdue for processing

e.g. “Open Sales Documents”

▪ Lead time figures measure processing time from a defined start point to

a corresponding end point of a business process e.g. “Sales Document

Item Creation to Invoice Creation”

▪ Exception figures collect the number of error messages that occurred

during a business transaction e.g. “Failed Goods Movements During

Production Order Confirmation”*

▪ Automation rate figures measure the ratio of how many documents have

been processed automatically vs. manually within a certain time frame

e.g. “Automation rate: Process orders”**

Process Structure Example:

▪ Lead-to-Cash

▪ Order-to-Cash

▪ Manage customer order

▪ Open sales orders

▪ Incomplete sales

documents

▪ Sales documents with

delivery block

▪ …

End-to-End Process

Sub-End-to-End

Process

Key

Performance

Indicators

(KPIs)

Process

*KPI category not available for SAP SuccessFactors **KPI category not available yet


Introduction to predefined content


Lead-to-Cash

Source-to-Pay

Design-to-Operate

✓ Sales Document Item Creation to Invoice Creation

✓ Sales Documents Created

✓ Sales Document Items Created

✓ Sales Documents with Delivery Block

✓ Sales Documents with Credit Block

✓ Sales Documents Open and Overdue for Delivery

✓ Open Sales Documents

✓ Incomplete Sales Documents

✓ Sales Documents with Billing Block

✓ Sales Document Items Overdue for Billing

✓ Outbound Deliveries Overdue for Goods Issue

✓ Outbound Deliveries Created

✓ Deliveries Overdue for Billing

✓ Deliveries Overdue for Picking

✓ Throughput of Outbound Goods Movements

✓ Sales Invoices Not Posted to Accounting

✓ Overdue Open Items in Accounts Receivable

(Customer Items)

✓ Sales Invoice Line Items Created

✓ Sales Invoices Posted

✓ Financial Postings

✓ Financial Line Items Posted

✓ Open Items in General Ledger Accounts (FI-GL)

✓ Purchase Order Items Created

✓ Open and Overdue Purchase Requisition Items

✓ Purchase Requisition Items Created

✓ Purchase Orders Created

✓ Open and Overdue Purchase Order Items

✓ Blocked Purchase Order Items

✓ Throughput of Inbound Goods Movements

✓ Inbound Deliveries Created

✓ Inbound Deliveries Overdue for Goods Receipt

✓ Supplier Invoice Items Blocked for Payment

✓ Supplier Invoices Created

✓ Overdue Open Vendor Items in Accounts Payable

✓ Production Orders Overdue for Final Confirmation

✓ Production Orders Overdue for Delivery Completion

✓ Production Orders Overdue for (Technical) Closure

✓ Process Orders Overdue for Release

✓ Process Orders Overdue for Final Confirmation

✓ Process Orders Overdue for Delivery Completion

✓ Process Orders Overdue for (Technical) Closure

✓ Production Orders Overdue for Release

✓ Planned Orders with Opening Date in the Past

✓ Failed Goods Movements During Production Order

Confirmation

✓ Failed Goods Movements During Process Order

Confirmation

✓ Process Orders Created

✓ Production Orders Created

✓ Plant Maintenance Orders or Customer Service Orders

Created

SAP Business Suite

SAP S/4HANA, private cloud

editionSAP S/4HANA

Cloud

SAP S/4HANA

See all available KPIs online


Available KPIs for Lead-to-Cash, Source-to-Pay, and Design-to-Operate

https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/business-process-monitoring/business-process-monitoring-kpis.html



Available KPIs for Recruit-to-Retire

See all available KPIs online.

SAP

SuccessFactors

Recruit to Retire

✓ Job Requisitions Created

✓ Job Requisitions with Applications

✓ Job Requisitions Without Applications

✓ Job Requisitions Closed

✓ Job Requisition to Hiring (Time to Hire)

✓ Candidates Created

✓ Job Applications Created

✓ Job Applications in Status "Applied"

✓ Job Applications in Status "Not Applied"

✓ Job Offers Created

✓ Job Offers Pending

✓ Job Letters Created

✓ Job Letters Pending

✓ Send Date of Offer Letter to Candidate Response

✓ Contracts Created

✓ Contracts Created to Employee Start Date

https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/business-process-monitoring/business-process-monitoring-kpis.html


Get transparency on your

process performance:

▪ E2E process visualization with

business process KPIs out of

the box

▪ Analyze and drill-down to

document level


Available dashboards



Demo: Blocked sales documents for Lead-to-Cash


… with business process monitoring

they monitor their end-to-end process.

YourOfficeSupply is an online wholesaler

for office supplies …

… they are using

SAP S/4HANA Public Cloud Edition

to run their Order-to-Cash process and ...

Lead-to-Order Order-to-Cash

SAP Cloud ALM

business process

monitoring

YourOfficeSupply




Ed Adams, 39Customer AB Logistics Ltd.

Premium customer of

YourOfficeSupply

Urgently needs new office

materials and orders

them through the web

shop via express order.

Rafael Smith, 34Order Processing Agent

Responsible for timely

order fulfilment

Receives automatic alert

notification on high number

of blocked sales orders.

Starts root-cause analysis

and resolves the issue.

Ed Adams, 39Customer AB Logistics Ltd.

Premium customer of

YourOfficeSupply

Receives the ordered office

materials in time and enjoys

the great customer experience

with YourOfficeSupply.




Order processing agent’s desk

Rafael Smith, 34Order Processing Agent

Responsible for timely

order fulfilment

Rafael receives a new alert notification. He

checks for the root cause of the critical blocked

sales documents of the customer AB Logistics

and initiates a workflow.

SAP Cloud ALM –

business process

monitoring







Next day at AB Logistics’ headquarters

Ed Adams, 39Customer

AB Logistics Ltd.

Great, I have just received the office materials!

This was a really great customer experience.

I will definitely return to YourOfficeSupply.





Hands-On



Summary

You have learned that:

▪ Business process monitoring makes the daily

performance of the end-to-end processes transparent

and helps to ensure business continuity.

▪ Predefined process content and key performance

indicators (KPIs) for the end-to-end processes are

provided by SAP.

▪ Basis for an efficient problem resolution is the

embedded alerting, embedded analytics and offering

of an automated problem resolution.

In the next unit you will learn:

▪ How to set up and use integration and exception

monitoring

Thank you.

Contact information:

[email protected]

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of

SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its

distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or

warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.

The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty

statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional

warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or

any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,

and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and

functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason

without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or

functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ

materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they

should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered

trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names

mentioned are the trademarks of their respective companies.

See www.sap.com/trademark for additional trademark information and notices.

www.sap.com/contactsap

Follow all of SAP

http://www.sap.com/trademark

https://www.sap.com/registration/contact.html

https://plus.google.com/+SAP

https://www.linkedin.com/company/sap

https://www.youtube.com/user/SAP

https://twitter.com/sap

https://www.facebook.com/SAP


Unit 2: Integration and Exception Monitoring


Integration and exception monitoring

Overview

▪ End-to-end monitoring by

correlating single messages

to end-to-end message

flows across cloud services

and systems

▪ Monitoring of integration-

related exceptions

▪ Support of peer-to-peer

interfaces as well as

orchestrated integration

▪ Supports efficient problem resolution process and

collaboration between business and IT:

− Monitoring to visualize healthiness of integration aspects

− Alerting to inform responsible persons in business and IT

− Search and track to identify business-driven problems

− Analytics to analyze identified critical issues

− Operation automation to trigger corrective activities

Cloud

On-Premise

SAP Integration Suite Cloud Integration

SAP S/4HANA

SAP S/4HANA

Cloud

Integration and Exception

Monitoring



What’s in it for you?

▪ End-to-end monitoring by correlating single integration artifacts

to end-to-end message flows across components and across

technology

▪ Embedded monitoring of integration-related exceptions

▪ Support of message flows processed by platforms like SAP

Integration Suite as well as support of peer-to-peer interface

technologies as AIF messages as part of SAP S/4HANA Cloud

▪ Search and track single messages based on exposed business

context attributes like order number

▪ Embedded alerting to inform integration owner in IT about critical

issues including drill-down in alert details

▪ Integration with operation automation to trigger operation flows

context-sensitively

▪ Intelligent housekeeping (planned) to minimize necessary data

volume w/o losing RCA context

▪ Embedded analytics (planned) to enable root cause analysis

based on historical and aggregated data → Identify trends and

compare different time periods



High level architecture

IM

Application

Event

AssemblerNormalized

Event Store

Import from LIS

Clo

ud

Pro

du

cts

IM API

IM API

IM API

Cloud Service 1

Cloud Service 2

Cloud Service 3

pull

push

End-User Input

Registration via Cloud Service

Message ID = 123

TransID=abc

Message ID = 231

TransID=abc

PrevCompID=CS1

Message ID = 321

TransID=abc

PrevCompID=CS2La

nd

sc

ap

e

Ma

na

ge

me

nt

Inte

gra

tio

n

Mo

nit

ori

ng



Configuration

Prerequisites

▪ Register managed systems and services to SAP Cloud ALM

− Registration strategy depends on the managed service or system type

and if they use PUSH or PULL data collection

− For information, follow the documentation in the SAP Cloud ALM

Expert Portal

Configuration

▪ Standard Setup:

− Simple activation of standard monitoring content without additional

customizing (literally “push a button”)

▪ Expert Setup:

− Allows the activation and deactivation of specific monitoring categories

− Allows the creation of alerts for the collected data

▪ Scenario Configuration:

− Allows the visualization of relationships between components and to

maintain message paths

https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/integration-monitoring/int-mon-setup-support.html



Standard setup

▪ SAP Cloud ALM contains standard monitoring

content for the connected services and systems

depending on the service and system type

▪ Standard content can be activated without further

configuration

Setup steps:

1. Select the systems you want to configure in the

scope selection

2. Open the Configuration tray using the button

3. Switch the lever from Off to On for the service or

system for which you want to activate the

monitoring



Expert setup

▪ In the Expert setup you can

− Deactivate single monitoring categories

− Create alerts for which you can set up notification in

intelligent event processing

− Restrict the alerted artifacts using monitoring category-

specific filters

Setup steps for the Expert setup

1. Click the icon in the Configuration tray

2. Activate or deactivate monitoring categories on the

‘Monitoring’ tab

3. On the ‘Alerting’ tab you can create as many alerts as you

need and use the alert parameters to filter for specific

errors and messages



Event processing

* For detailed information please watch the unit on intelligent event processing in week 3

▪ Alerts created in integration and exception monitoring create

events that can be processed in intelligent event processing

Setup steps for event processing

1. Open Intelligent Event Processing

2. Create a new event processing rule

− Enter a name for the rule

− Select type ‘Integration Monitoring Event’

− Enter the alert name and the alert context

− Enter the recipient from the verified recipients in

Notification Management



Integration scenarios

▪ In SAP Cloud ALM the collection for messages and

exceptions is maintained on services or system level

▪ Scenarios allow you to visualize a relationship between

components and to maintain message paths

Setup Steps:

1. In the scenario configuration, select the services and

systems that are part of you scenario

2. Add filters on component level to include only messages

and exceptions relevant for the scenario

3. Maintain message paths between components



Setup demo



Usage

Integration and exception monitoring features:

▪ Message monitoring

▪ Message search (tracking)

▪ Alerting on failed messages or exceptions



Monitoring – overview

▪ The message summary contains a list of all message

interfaces for which messages ran over the component

in the selected timeframe

▪ The message list contains each message flow that ran over an interface

in the selected time frame

▪ The Monitoring view provides

a detailed status overview per

service or system on the

incoming/outgoing messages

for different interfaces

▪ Interfaces are presented by

monitoring categories



Monitoring – Message Details

▪ In Message Details you find the status details for the

message flow

▪ You also find each component the message was processed

in, and related messages (e.g. acknowledgements or

retries)

▪ By selecting a component you can access the instance of

the message on this component

▪ By selecting the message in the ‘Related Messages’ table

you can see the status and application data for the selected

message

− Status Details: Contains the status information and

processing timestamps and information for the message

− Application Data: Contains collected context attributes for

the message, e.g. object references, technical context

like business system information or reported business

context



Monitoring – Tracking

▪ Tracking allows users to search and track single messages

based on specific business or application context attributes

like the order number, employee ID, object reference,

component name, etc.

▪ As a prerequisite, context information must be exposed by

the relevant component and sent together with the

message's log fragments to SAP Cloud ALM

▪ The search is executed cross-component and cross-

category



Monitoring – Alerting

▪ Based on the collected data, alerts for

certain error situations can be defined,

e.g. messages in status ERROR on a

specific component or in a specific

scenario

▪ Generated alerts are collected into the

Alert Inbox

▪ The alert contains each message that

contributed to the alert creation

▪ In the alert details you can perform

actions like assign a processor, add

comments, or confirm an alert, send a

notification, or start an operation flow



Usage demo



Summary

In this unit you learned:

▪ How to set up integration and exception monitoring

▪ How to use integration and exception monitoring to monitor

message flows and exceptions


▪ How to set up and use real user monitoring

For further information and supported products, please

refer to the SAP Cloud ALM Expert Portal

https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/integration-monitoring.html

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 3: Real User Monitoring


Real user monitoring

Overview

Browser or

Mobile Device

Cloud Service Cloud Service

Real User and Performance

Monitoring

On-Premise

System

▪ Provides transparency regarding performance as experienced by end

users as well as the utilization of business functionality

▪ Measurement at frontend and server side to identify actual root cause

of performance problems (frontend, network, cloud services and/or

systems)

▪ Utilization of SAP Passport technology allows to correlate performance

data measured at frontend, cloud service and/or system side



Benefits

Real user monitoring provides transparency about:

▪ Which applications are most used by the end users and

▪ What are the relevant end-user response times

Within the application you can:

▪ Identify single requests that show poor performance for a

specific execution

▪ Review the execution frequency of a specific application or

function

▪ Access the request flow and view the analysis that includes

all components involved in a request flow execution

▪ Analyze the resource consumption of each sub-request.

For example, review the time that was spent by a single

sub-request for a component

▪ Customize your request types with personalization features.

Filter by timeframe, request name, and request type



Scope

Real user monitoring in Cloud ALM collects data for

the following request types:

▪ SAPUI5/Fiori

▪ SAP Web Dynpro

▪ SAP GUI for HTML

▪ HTTPS

The following solutions are supported

▪ SAP S/4HANA Cloud

▪ SAP S/4HANA

▪ SAP Business Suite

▪ SAP Marketing Cloud



How does it work?

SAP S/4HANA CE,

SAP IBP,

SAP Marketing Cloud,

SAP BTP (Neo)

Browser (PC or

Mobile Device)

Frontend System

(Gateway)Backend Systems

Passport (incl. Transaction

ID, Root Context ID, …)

IT Analyst

Business

Analyst

End UsersSAP Cloud ALM

Real-User Monitoring

Receiv

er

Reader

Single

Requests

Aggregated

Requests

Correlated

RequestsCorrelator

End-user performance is measured on the client side (browser or SAP GUI). Backend statistics records

(GW, ABAP, etc.) are collected and transferred to SAP Cloud ALM. Collected data is assembled and

correlated in SAP Cloud ALM to end-to-end real-user scenarios.



Configuration

Prerequisites

▪ Configure the PUSH data provider for the managed

ABAP system or public cloud service

▪ Make sure to select “Performance Monitoring” in the

use-case selection of the PUSH data provider setup

Setup

▪ No additional setup is required



Usage – Overview

Scope

Selection

Time Frame

Selection

Overview

▪ Use this screen to identify

services and/or request types

with poor performance

▪ You can adjust the selected

services in scope as well as the

time frame considered for the

analysis

➢Select the service or the

request type you want to

analyze to drill-down



Usage – Request Overview

Request Overview

▪ In this first drill-down you can

identify the requests with poor

performance or very high usage

for the selected service / request

type

▪ The table is sorted so you see

the request with the most red

executions first. You can adjust

the sort order by clicking on the

column header

➢Select the request name you

want to analyze to drill-down



Request rating

The rating of the requests depends

on the response time.

For every request action (e.g. a GET

in a particular HTTPS request) the

response time is compared with the

median of all former response times

of that category.

If the response time is at least 12

times as long as this median, the

status is Critical (color red); if it is at

least 4 times as long, the status is

Warning (color yellow).



Usage – request details

Request details (actions)

▪ On this screen you see the

different actions performed for

the request selected in the

previous screen

➢Select the action you want to




Usage – request details

Request details (time)

▪ On this screen you can see each

execution and the execution

time for the selected action

➢Select the execution you want to




Usage – request flow

Request flow

▪ The request flow allows the

analysis of the single request

flow, including all components

involved in the execution

▪ For browser-based requests

you can see the UI technology,

the browser, and the OS

version

▪ For each component you see

the approximate percentage the

request spent in the component



Usage – Analysis view

Analysis view

▪ The Analysis view provides a

flexible selection of metrics

and dimensions for analysis

▪ You can download the analysis

data into an Excel file for further

processing

▪ Available metrics:

− E2E Response Time

− Backend Time

− Network Time

− Executions

▪ Available Dimensions:

− Application/Request Name

− Request Type

− User Name



Demo



Summary


▪ How real user monitoring helps you monitor performance

and availability

▪ How to set up real user monitoring

▪ How to use real user monitoring


▪ How to set up and use job and automation monitoring

For further information please refer to the SAP Cloud

ALM Export Portal

https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/real-user-monitoring.html

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 4: Job and Automation Monitoring


Job and automation monitoring

Challenge for the customers

Jobs and automated actions like workflows are the

backbone of business processes that span across

several of a customer’s SAP cloud and on-premise

products.

For business continuity, customers need to ensure that

all automations are running successfully, which means

that they

1. run on time / within an expected recurrence pattern

2. finish successfully

3. process their data without errors and warnings

4. do not deteriorate regarding their run time

Customers face the challenge of having an overview on

job execution in a distributed heterogenous landscape.

Job 1

Customer Landscape

(Cloud and On-Premise)

Job Monitoring

Automation Elements of End-to-End Processes

Job 2 Job n

Visualize automation process performance and disruptions

Identify automation process disruptions and exceptions



Benefits of job and automation monitoring

Job and automation monitoring provides a central

platform to answer whether automation processes

have finished on time, and within the expected run

time and without exceptions:

You can:

▪ identify automations showing exceptional behavior regarding

– execution status

– application status

– run time

– start delay

▪ drill down into individual executions and forward-navigate to

the managed cloud service

▪ receive alerts and notifications in case of issues with

automations

Planned is analytical help to identify automation issues

before they occur



How does it work?

SAP Cloud ALM Job & Automation Monitoring

Jobs and automated actions are defined and executed in the managed cloud and on-premise services. The individual

executions are captured (start, end times, and status) by the local job execution infrastructures. The customer can choose

to forward job execution data to SAP Cloud ALM, where the individual execution data is assembled and correlated with job

definition data.

SAP Cloud Service A

SAP On-Premise Service B

Execution of Job A

Execution of Job AExecution of Job D

Execution of Job EExecution of Job E

Execution of Job C

Execution of Job E

Execution of Job C

Execution of Job D

Execution of Job F

Execution of Job HExecution of Job G

Execution of Job BExecution of Job B

Execution of Job F

Execution of Job G

Execution of Job H

Execution of Job F

Service B

Job B

1. Execution of Job B

2. Execution of Job B

Job H

1. Execution of Job H

2. Execution of Job H

Job F

1. Execution of Job F



Job G

1. Execution of Job G



Service A

Job A

1. Execution of Job A

2. Execution of Job A

Job C

1. Execution of Job C

2. Execution of Job C

Job D

1. Execution of Job D

2. Execution of Job D

Job E

1. Execution of Job E





Scope of job and automation monitoring

Job and automation monitoring in SAP Cloud ALM currently supports

monitoring of the following job types (the scope is continuously

enhanced):

▪ SAP S/4HANA application jobs

▪ SAP Intelligent RPA jobs

Planned for Q3 2021 is

▪ SAP ERP Central Component

– Application jobs

– ABAP jobs

– BW process chains

The following solutions are supported regarding automations:

▪ SAP S/4HANA Cloud

▪ SAP Marketing Cloud

▪ SAP Integrated Business Planning

▪ SAP Intelligent Robotic Process Automation



Setup and configuration

Prerequisites

▪ You need to have the authorization for job and automation

monitoring in SAP Cloud ALM

Setup

▪ The managed cloud or on-premise service needs to be

connected to SAP Cloud ALM. For this, service-dependent

configuration needs to be done as documented in

https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-

portal/job-monitoring/job-automation-monitoring-details.html

Configuration

▪ For monitoring and analytics, no setup is required.

▪ To receive alerts in case of job failures, you need to perform

some configuration steps as described in the Expert Portal.

https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/job-monitoring/job-automation-monitoring-details.html



Usage (1)

Getting an overview on the overall job

situation

▪ Overview provides information on the job

and automation status of all the services that

feed data

▪ You can drill down into the list of jobs that

show exceptions

▪ You can drill down into the list of alert

situations



Usage (2)

Getting an overview on the job

situation per service

▪ Monitoring provides information on

the job and automation situation per

service

▪ You can drill down into the list of jobs

per service

▪ Every job is rated based on its last

execution regarding

− Execution Status

− Application Status

− Start Delay

− Run Time



Usage (3)

Understanding former

executions for a failing job

▪ From an individual job you can drill

down into the list of executions

▪ From an individual execution you

can forward-navigate into the

managed service

Navigation via direct

link to managed

service.



Usage (4)

Alerts for failing job

executions

▪ Alerting is offered for all metrics:

− Execution Status

− Application Status

− Start Delay

− Run Time

Navigation via direct link to

managed service.

▪ In the monitoring view you

can see if there are open

alerts

▪ In the alerting view you can

filter for a job name

▪ From the alert you can

forward-navigate into the

managed service in the same

way as for monitoring



Demo



Summary


▪ That the job and automation monitoring application helps

you to monitor the performance and availability of your

automation processes

▪ The basic and generic concept of the job and automation

monitoring application

▪ How to use the job and automation monitoring application


▪ How to set up and use health monitoring

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 5: Health Monitoring


Health monitoring

Check the healthiness of cloud services and systems

Health Monitoring

Subscribed Cloud

ServicesCustomer On-

Premise Systems

Monitoring Analytics Alerting

Health status, metrics

▪ Visualizes the health of cloud services and

systems to identify service disruptions or

degradations

▪ Health monitoring is planned to be enhanced with

embedded alerting, including predefined

operation flows to trigger corrective actions e.g.

service restarts

▪ Allows to execute application health checks for

SAP cloud services to check the status of

components, certificates, connectivity, …

▪ Supports health checks for cloud services and

on-prem systems, including trends and usage

metrics

▪ Provides embedded analytics to identify the root

cause of discovered problem


Health monitoring

Usage

Health monitoring is used for

▪ Self-monitoring for SAP Cloud ALM

▪ Monitoring of cloud services

− SAP Integration Suite (Cloud Integration)

− SAP Intelligent Robotics Process Automation

▪ Monitoring of managed ABAP systems


Health monitoring

Usage – overview

▪ Health Monitoring Overview provides

a status overview for all connected

managed services and systems


Health monitoring

Usage – SAP Cloud ALM self-monitoring

▪ SAP Cloud ALM self-monitoring is

automatically activated for the SAP Cloud

ALM tenant

▪ Self-monitoring monitors metrics like:

− SLIS import job

− Number of cloud services and systems

− Number of endpoints for the SAP Cloud

ALM use cases

▪ Metric reporting is available for all metrics

out-of-the-box


Health monitoring

Usage – monitoring for managed services and systems

* Distributions represent the unattended tasks that are executed on unattended agents

Health monitoring for supported managed

services and systems focuses on metrics

related to the technical health of the

underlying systems or services:

▪ ABAP systems:

− ABAP basis metrics like

• System exceptions like short dumps,

• System resources like work processes,

• System performance like response times etc.

▪ SAP Integration Suite (Cloud Integration):

− JMS queue status, performance, and capacity

▪ SAP Intelligent Robotics Process Automation:

− Planned, processed, and running distributions*


Health monitoring

Configuration

Health monitoring uses PUSH and PULL data collection

depending on the managed service or system

Setup

1. Register the managed service or system by creating an

endpoint or enabling PUSH data collection accordingly

− Make sure to select the “Health Monitoring” use case during

endpoint creation / the PUSH setup

2. Activate data collection in the health monitoring application

for managed services and systems using PULL data

collection

− For services and systems using PUSH data collection, the data

collection is automatically activated

For more information, refer to SAP Cloud ALM Expert Portal

https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal.html


Health monitoring

Demo


Health monitoring

Summary


▪ How health monitoring helps you to monitor the

health of SAP Cloud ALM and its connected services

and systems

In the next week you will learn:

▪ How to handle events from the SAP Cloud ALM

monitoring applications by creating alerts and

notifications and starting automations

Thank you.


[email protected]










warranty.














Follow all of SAP








Date post:	01-Jan-2022
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times