SAP HANA Scale-Out Monitoring

SAP HANA Scale-out means combining multiple independent nodes in one system. SAP HANA systems that are remotely configured in IT-Conductor are monitored by distributing the tenant databases across multiple nodes.

IT-Conductor provides monitoring of multiple databases such as system DB and tenant databases. They are observed as separate elements, but each tenant is monitored like other primary tenant databases. Furthermore, IT-Conductor offers a drill-down feature for further analysis, correlated alerts, operational status, and performance metrics across applications/DB/OS. The platform also provides time-correlated information about how the monitored system functions and performs.

Configure HANA Systems for Monitoring in IT-Conductor

Note: To learn more about configuring SAP HANA Systems in IT-Conductor, kindly refer to this article.

In the Administrator dashboard, navigate to HANA Systems.

Figure 1: SAP HANA Systems in Administrator Dashboard

The page will show the list of HANA Systems defined in IT-Conductor.

Figure 2: Sample List of SAP HANA Systems

Clicking the <System Name> will give all the configured inputs when the system is first added to IT-Conductor for monitoring. The next page will show the details such as the System ID, Role, Host, Tenant Database, etc.

Figure 3: SAP HANA System Properties

SAP HANA Tenants Monitoring in IT-Conductor

Every tenant database is monitored separately. Important features such as availability, alerts, and services are integrated into IT-Conductor for detailed monitoring.

Figure 4: SAP HANA Tenants in Service Grid

An SAP HANA node contains the CPU, memory, response times, threads, requests, and volume information to be tracked. Individual nodes in a distributed system have different roles (master, slave, or none) depending on the task.

Figure 5: SAP HANA Services Monitoring

As mentioned, IT-Conductor offers a drill-down function providing more detailed information about the monitoring features. Clicking on the triangle icon to expand the grid or the graph icon will give the graphical charts where you can compare each component easily. This also enables administrators to troubleshoot faster with root cause analysis.

Figure 6: Expandable Icons

Figure 7: Sample Charts for Thread Monitoring

Alerts

Performing regular checks on the status, performance, and resource usage is part of the continuous internal monitoring of a system. When configurable threshold values are exceeded, it issues alerts. Alerts can be monitored in individual tenant databases. When the alerts are triggered, they can potentially impact the system’s overall health.

Figure 8: Sample Chart for Alert Monitoring

SQL Statements

In addition to the performance metrics overview, IT-Conductor can also give comprehensive information about SQL statements with just a click on the graph. SQL statements give a high-level overview of the database’s workload.

Figure 9: Sample SQL Statement

Linux Monitoring

Linux monitoring is also supported by IT-Conductor. Providing the SSH parameters will add the nodes to the monitoring platform. IT-Conductor automatically discovers Linux servers to monitor File Systems (if any) and important system metrics such as the CPU and memory utilization to know how much memory is used.

Figure 10: Linux Monitoring in SAP HANA

Video