Monitoring in SAP HANA Enterprise Cloud

A High-Level Overview
CUSTOMER
Document Owner:
SAP Managed Cloud Delivery – Service Engineering

March 2017 Version 2.0

MONITORING IN SAP HANA ENTERPRISE CLOUD – MARCH 2017 VERSION 2.0

TABLE OF CONTENTS
1 INTRODUCTION ............................................................................................................................... 4
2 MONITORING STRATEGY AND ARCHITECTURE ........................................................................ 4
2.1 System Stack and Monitoring ...............................................................................................................4
2.2 MCD Monitoring ......................................................................................................................................5
2.3 Application and Database Monitoring ..................................................................................................5
2.3.1 Infrastructure Monitoring ...........................................................................................................................5
2.4 High-level Architecture of F-Run based Monitoring ...........................................................................6
2.4.1 Central Component ...................................................................................................................................6
2.4.2 Distributed Component .............................................................................................................................6
2.4.3 Optional Distributed Component: .............................................................................................................6
2.4.4 Communication between F-Run and Managed System ...........................................................................7
2.5 Usage of F-Run and MCD Nagios for HEC monitoring .......................................................................7
2.5.1 Storage of collected information ...............................................................................................................7
2.6 Role of customer in monitoring ............................................................................................................8
3 SECONDARY MONITORING ........................................................................................................... 8
4 MONITORING KPI ............................................................................................................................ 9
4.1 HANA DB .................................................................................................................................................9
4.2 Sybase ASE DB .....................................................................................................................................10
4.3 MSSQL DB .............................................................................................................................................10
4.4 MaxDB ....................................................................................................................................................10
4.5 ABAP ......................................................................................................................................................10
4.6 JAVA ......................................................................................................................................................11
4.7 BOE ........................................................................................................................................................11

© 2017 SAP SE or an SAP affiliate company CUSTOMER 2

MONITORING IN SAP HANA ENTERPRISE CLOUD – MARCH 2017 VERSION 2.0

Copyright and Disclaimer

Copyright © 2017 SAP AG. All rights reserved.

THIS DOCUMENT IS PROVIDED BY SAP SE AND ITS AFFILIATED COMPANIES ("SAP GROUP") FOR
INFORMATIONAL PURPOSES ONLY, WITHOUT REPRESENTATION OR WARRANTY OF ANY KIND, AND
SAP GROUP SHALL NOT BE LIABLE FOR ERRORS OR OMISSIONS WITH RESPECT TO THE MATERIALS.
NOTHING CONTAINED HEREIN SHALL BE CONSTRUCTED TO BE A LEGALLY BINDING AGREEMENT
UNDER INTERNATIONAL LAW. THIS DOCUMENT DOES NOT MODIFY, SUPPLEMENT, DIMINISH, OR IN
ANY WAY AFFECT ANY AGREEMENT BETWEEN SAP OR AN SAP AFFILIATE AND ANY THIRD PARTY.

NO PART OF THIS DOCUMENTATION MAY BE REPRODUCED OR TRANSMITTED IN ANY FORM OR FOR

ANY PURPOSE WITHOUT THE EXPRESS PERMISSION OF SAP SE. ALL CONTENT IS CATEGORIZED AS
CONFIDENTIAL INFORMATION OF THE SAP GROUP.

THIS DOCUMENT IS INTENDED AS BACKGROUND INFORMATION AND DESCRIBES INTERNAL

PROCESSES OF SAP GROUP AND TECHNICAL DETAILS OF SOME ASPECTS OF THE HANA
ENTERPRISE CLOUD SERVICES.

ANY PROCESSES DESCRIBED AND INFORMATION GIVEN IN THIS DOCUMENT ARE SUBJECT TO
CONTINUOUSLY IMPROVEMENT PROCESS. THAT MEANS THE TECHNICAL CONCEPTS AND
PRACTICES USED TO ACHIEVE THE SERVICES DESCRIBED IN THIS DOCUMENT ARE EXPECTED TO
CHANGE OVER TIME BY SAP GROUP. SAP GROUP RESERVES EXPLICIT THE RIGHT TO CHANGE ANY
CONTENT OF THIS DOCUMENT WITHOUT PRIOR NOTICE.

© 2017 SAP SE or an SAP affiliate company CUSTOMER 3

MONITORING IN SAP HANA ENTERPRISE CLOUD – MARCH 2017 VERSION 2.0

1 INTRODUCTION
This document explains the technical concepts around system monitoring in HEC.

The purpose of monitoring is to minimize the risks of harming or even completely interrupting the customers’
business processes, due to improperly running components in the productive system landscape. SAP leverages
the latest technologies, best practices, and a 24x7 operations team to ensure we meet the availability SLA, to
ensure the health of customer systems, and to constantly improve the overall service experience for our
customers.

The monitoring includes application components and infrastructure components. Active monitoring allows us to
respond to issue detection, enabling proactive intervention and quick reaction to critical incidents.
Monitoring tools are configured on individual servers during the setup and will be integrated with the
infrastructure layer tools, monitoring cockpit, incident management and continuous improvement systems.

2 MONITORING STRATEGY AND ARCHITECTURE

2.1 System Stack and Monitoring

The SAP HEC monitoring scope consists of specific checks on each of the layer mentioned up to and including,
for example, the SAP NetWeaver operations layer. According to the standard HEC contract, the standard
excludes the following. (Coverage is possible with Application Management Services add. to standard HEC
contract):

Job monitoring, IDOC, PI queue monitoring, and so on, according to the HEC Roles & Responsibilities matrix.

© 2017 SAP SE or an SAP affiliate company CUSTOMER 4

MONITORING IN SAP HANA ENTERPRISE CLOUD – MARCH 2017 VERSION 2.0

2.2 MCD Monitoring

The following Monitoring Infrastructure supports the HEC Managed Systems Operations.

2.3 Application and Database Monitoring

 Multi-instance monitoring based on Solution Manager switched to SAP HANA-based solution “Focused Run
for SAP Solution Manager” (aka SimpleRunSolMan) specifically covering the needs for cloud service
providers.
 This allows for a maximum degree of standardization, simplification, automation, and scale-out for each
customer.
 Nagios serves as the secondary and complementary monitoring tool which handles
o Downtime/Emergency of main monitoring
o Flexibility to easily extend MCD portfolio for special requests

2.3.1 Infrastructure Monitoring

Servers are provisioned through our internal provisioning tool and monitored by Nagios. The alerts are forwarded
and processed in our infrastructure ticketing tool.

The following tools are described in the figure below:

a) Focused-Run, aka Simple Run Solution Manager (SRSM) for Application and Database monitoring
b) Nagios Incinga2, as secondary monitoring tool for Application and Database monitoring
c) Infrastructure Monitoring tool and alert inbox, for infrastructure alerts
d) Service Provider cockpit, serving as alert inbox for monitoring and processing alerts related to
Application and Database monitoring.

© 2017 SAP SE or an SAP affiliate company CUSTOMER 5

MONITORING IN SAP HANA ENTERPRISE CLOUD – MARCH 2017 VERSION 2.0

2.4 High-level Architecture of F-Run based Monitoring

The following section describes the high-level architecture of F-Run (SRSM) based monitoring environment as
well as the communication between the managed customer system and the central monitoring component.

2.4.1 Central Component

The F-Run (aka SRSM) monitoring consists of the following central components:

a) ABAP Stack: Running the application and UI

b) HANA DB: Data persistency

2.4.2 Distributed Component

The F-Run (aka SRSM) monitoring consists of the following distributed components:

a) SAP Host Agent (SHA): Running on each (customer) host

b) Simple Diagnostics Agent (SDA): Running on each (customer) host
c) Introscope Enterprise Manager (IS EM): Running once per customer network
d) Introscope Byte Code Injection Agent (IS BCIA): Deployed on non-ABAP Systems for performance
metric and trace collection
e) ST-PI and ST/A-PI: ABAP data collectors developed for SRSM are delivered with ST-PI and ST/A-PI

2.4.3 Optional Distributed Component:

a) Proxy: Control/secure requests from admin network to customer network
b) Reverse Proxy: Control/secure requests from customer network to admin network.
c) SAP Landscape Data Router (SLDR): For customers with special SLD DS forwarding needs

The following figure shows the major components for SRSM monitoring:

© 2017 SAP SE or an SAP affiliate company CUSTOMER 6

MONITORING IN SAP HANA ENTERPRISE CLOUD – MARCH 2017 VERSION 2.0

2.4.4 Communication between F-Run and Managed System

By default, F-Run Applications use Hypertext Transfer Protocol (HTTP) as the application layer protocol.

The following figure shows the communication between F-Run (SRSM) and the customer network:

2.5 Usage of F-Run and MCD Nagios for HEC monitoring

Agents installed on the central communication server available per customer network are collecting the
monitoring data of the managed system and forwarding it to the central F-Run instance.

A dedicated team of experts develops new monitoring checks. The framework allows you to use configuration
setting templates (provided by SAP), which then can be modified and distributed to other components.

The HEC support team adjusts and applies those checks.

The Technical Monitoring and Alerting as part of F-Run or MCD Nagios offers central monitoring of the
performance and health of systems. Alert correlation and propagation capabilities avoid alert flooding.

2.5.1 Storage of collected information

The information collected from the different Managed Objects is stored in different places:

a) Reporting: Relevant metric data will be stored within the BOBJ-based Cloud reporting store managed by
the Data Provider connector.
b) Monitoring: Relevant metric data will be stored in the F-Run monitoring system
c) Alerting: Created alerts are forwarded to the central Alert Inbox.

MCD Nagios is used for backup and complementary monitoring. In this case, the data collection from systems is
performed by the MCD Nagios agents. The Monitoring infrastructure from MCD Nagios is completely different
and separate from the infrastructure

© 2017 SAP SE or an SAP affiliate company CUSTOMER 7

MONITORING IN SAP HANA ENTERPRISE CLOUD – MARCH 2017 VERSION 2.0

2.6 Role of Customer In Monitoring

If any additional monitoring related to the application is required, the customer and its operation teams need to
configure it. In addition, the customer operations teams will need to handle the regular monitoring and routine
alert-handling activities. Customers can run an on-premise Solution Manager system which will enable them to
use SAP’s Monitoring activities, SAP Solution Manager, and SAP Diagnostics.

SAP will not forward the alerts directly to customers.

3 SECONDARY MONITORING
MCD Nagios is the secondary and standby monitoring tool during downtime of Solution Manager or unavailability
of SPC. Nagios also supports monitoring solution for special solutions where the SAP content is not yet
developed. The Nagios solution is completely separated from the primary monitoring solution and therefore no
dependencies in architecture/deployment exist.

Nagios allows you to enhance existing monitoring checks and create your own dashboards.

Figure: Nagios Architecture and Communication

© 2017 SAP SE or an SAP affiliate company CUSTOMER 8

MONITORING IN SAP HANA ENTERPRISE CLOUD – MARCH 2017 VERSION 2.0

4 MONITORING KPI
on the following tables provide the different parameters being monitored for major components. Other solutions
monitor similar parameters.

4.1 HANA DB
Availability
Database Host Status IQ DB: DBSpace Status
Database Unavailable Hana Cloud Connector Availability
Inactive Services Hana MDC Index Server Process
IQ DB: DBSpace File Status
Configuration
Database Recoverability log mode License Expiry
OVERWRITE Lock Wait Timeout Configuration
Delta Merge mergedog Configuration
Discrepancy between host server times
Exceptions
Disk Usage Schema Inconsistency
Existence of Data Backup Secure Store File System SSFS Availability
HEC Internal Solution Manager Metric Size of Diagnosis Files
Collection Problem SR: Connection between systems in system
Host Physical Memory Usage replication setup
Internal Disk-Full Event Status of Most Recent Log Backups
Number of Log Segments Unavailable Volumes
Pagedump Files
Record Count of Column-Store Table
Partitions
Performance
Delta Merge Duration MVCC Versions
Large Heap Areas Percentage of Transactions Blocked
Long-Running Blocking Situations Python Trace Activity
Long-Running Cursors Row Store Fragmentation
Long-Running Serializable Transactions Savepoint Critical Phase Duration
Long-Running Statements Size of Delta Storage of Column-Store
Long-Running Uncommitted Write Tables
Transactions Total Memory Usage of Column-Store Tables
Memory Usage of Main Storage of Column- Total Memory Usage of Row Store
Store -Tables

© 2017 SAP SE or an SAP affiliate company CUSTOMER 9

MONITORING IN SAP HANA ENTERPRISE CLOUD – MARCH 2017 VERSION 2.0

4.2 Sybase ASE DB

Availability
ASE BackUp Server available ASE JobScheduler available
ASE Database available ASE SRS Replication Status
Exceptions
ASE Backup Status ASE Log Space
ASE Critical Error Messages ASE Long Running Transactions
ASE Data Space ASE Warning Messages
ASE Error Messages
Performance

ASE Server State

ASE Replication Server Log Scan

4.3 MSSQL DB
Availability
MSSQL Database not available
Configuration
SQL Setup Check Message
Exceptions
MS SQL Error Log
MSSQL Backup
Performance
Autogrowth Status Free Space in File
Disk IO MS/Access Page Life Expectancy
Free Disk Space Percent of Transaction Log Used

4.4 MaxDB
Availability
MaxDB Availability MaxDB port
MaxDB kernel process MaxDB server process
MaxDB listener process

Exceptions
MaxDB Backup Status
MaxDB Database Structure Check

Performance
MaxDB Data Space

4.5 ABAP
Availability
ABAP Central Service not available
ABAP Instance not available
ABAP System not available
Configuration

© 2017 SAP SE or an SAP affiliate company CUSTOMER 10

MONITORING IN SAP HANA ENTERPRISE CLOUD – MARCH 2017 VERSION 2.0

Expiring ABAP certificates

Exceptions
Batch Job Errors
Enqueue Processing
High number of ABAP Short dumps
Performance
Not Enough Batch Resources
Not Enough Dialog Resources
Not Enough Gateway Resources
Spool Error
Update Processing
Not Enough ICM Resources
Not Enough Spool Resources
Not Enough Update Resources

4.6 JAVA
Availability
Java System not available Java instance not available
BPM Kernel Monitor ADS Instance Not Available
IDM Application Status CPS availability
Java Central Service not available Web Dispatcher not available

Configuration

Expiring J2EE certificates

Exceptions
Errors in BPM process instances
Errors in BPM tasks
Errors in Java Logs detected

Performance
High Enqueue Response Time
High Garbage Collection Activity
High Number of Long Running Threads
High Number of Used Application Threads
High Number of Used System Threads
Web Dispatcher ICM Cache Usage
Web Dispatcher ICM Connections
Web Dispatcher ICM Thread Number

4.7 BOE
Availability
Access Server Status BOE web applications not available
BOE Explorer Server not available Tomcat Server Availability
BOE Server not available Job Server Status

© 2017 SAP SE or an SAP affiliate company CUSTOMER 11

www.sap.com

© 2017 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.
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. Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices. 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 SE or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP SE 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 platform
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, which
speak only as of their dates, and they should not be relied upon in making
purchasing decisions.