This is in continuation of my previous Article Monitoring of SAP Systems Using Azure Monitors – Part I

6. DEPLOYMENT AND CONFIGRUATION

6.1 Configuring Azure Monitors

Go to Search for Azure Monitors for SAP Solutions

Click on New

Fill up all the requested details and Next

We can add the providers later, hence click on Next

Specify the Tags, if any and click Next

Review the settings and click on Review + Create

This will be initializing the deployment

Wait for the deployment to complete and then click on Go to resource

Now we can see the deployed Azure Monitors for SAP Solutions deployed

5.2 Creating Key Vault

As we need to securely store the secrets for accessing the SAP systems, for that we need to create Key Vault. To do so, Search for Key Vault and then click on Add

Fill out all the requested fields and then click on Next: Access Policy

Enable the access and click Next: Networking

Select the required network and then click on Next: Tags

Specify the tags if required and then click Next: Review + Create

Review all the settings and then click on Create

Wait for the deployment to get finished

Add the secret to Key vault and click on Create

Wait for the secret to save inside the key vault

5.3 Adding Providers

A provider contains the connection information for the corresponding component and helps to collect telemetry data from that component. One Azure Monitor for SAP Solutions resource can be configured with multiple providers of the same provider type or multiple providers of multiple provider types.

We can choose to configure different provider types to enable data collection from corresponding component in their SAP landscape.

We can also choose to configure multiple providers of a specific provider type to reuse the same SAP monitor resource and associated managed group.

It is recommended to configure at least one provider from the available provider types at the time of deploying the SAP Monitor resource. By configuring a provider, we can initiate data collection from the corresponding component for which the provider is configured.

If we don’t configure any providers at the time of deploying SAP monitor resource, although the SAP monitor resource will be successfully deployed, no telemetry data will be collected.

5.3.1 Configuring SAP HANA

We can configure one or more providers of provider type SAP HANA to enable data collection from SAP HANA database. The SAP HANA provider connects to the SAP HANA database over SQL port, pulls telemetry data from the database, and pushes it to the Log Analytics workspace in the subscription. The SAP HANA provider collects data every 1 minute from the SAP HANA database.

To add provider, we need to go to Providers in deployed Azure Monitor resource and click on Add

Select Type as SAP HANA and further details will be asked

Fill all the below connectivity details

• Input the Private IP for the HANA server.
• Input the name of the Database tenant you want to use. We can choose any tenant however, we are using SYSTEMDB here as it enables a wider array of monitoring areas.
• Input the SQL port number associated with your HANA database. The port number should be in the format of [3] + [instance#] + [13]. For example, 31013.
• Input the Database username you want to use. Ensure that database user has the monitoring and catalog read roles assigned.

Select for key vault which contains the secret for accessing HANA

Select the Key Vault and then click on Secret

Now click on Create

Wait for the connection to be Successful

5.3.2 Linux Operating System

We can configure one or more providers of provider type OS (Linux) to enable data collection from BareMetal or VM Node. The OS (Linux) provider connects to BareMetal or VM Nodes, using Node_Exporter endpoint, pulls telemetry data from the Nodes and pushes it to Log Analytics workspace in the customer subscription. OS (Linux) provider collects data every 60 seconds for most of the metrics from Nodes.

5.3.2.1 Installing Node Explorer

To install Node Explorer we need to go to page https://prometheus.io/download/ and download the required package

Transfer the package to OS and then extract the package

Navigate to the location of the extraction and start the Node Explorer

We can see the telemetry data populated on 9100 port

5.3.2.2 Adding OS Provider to Azure Monitor

To configure the OS (Linux) Provider, we need to add provide with following details and then click on Create

• Name – A name for this provider. It should be unique for this Azure Monitor for SAP solutions instance.
• Node Exporter Endpoint – Usually it should be http://<hostname>:9100/metrics

Wait for the connection to be established.

5.3.3 Configuring SAP NetWeaver

We can configure one or more providers of provider type SAP NetWeaver to enable data collection from SAP NetWeaver. NetWeaver provider leverages the existing SAPControl webservice interface to retrieve the appropriate telemetry information.

For the current release, below are the standard out-of-box SOAP web methods invoked by Azure Monitor.

Web Method	ABAP	JAVA	Metrics
GetSystemInstanceList	X	X	Instance Availability, Message Server, Gateway, ICM, ABAP Availability
GetProcessList	X	X	If instance List is RED, we can get what Process causing that server to be RED
GetQueueStatistics	X	X	Queue Statistics (DIA/BATCH/UPD)
ABAPGetWPTable	X	–	Work Process Utilization
EnqGetStatistics	X	X	Locks

To add provider, we need to go to Provider and then click on Add

Fill out the requested details: –

• Input the hostname of the SAP system and Subdomain (if applicable)
• Enter the Instance number corresponding to the hostname entered
• Enter the System ID (SID)

Wait for the provider to get successful connection to the system

5.3.4 Configuring High-Availability Pacemaker Cluster

We can configure one or more providers of provider type High-availability cluster to enable data collection from Pacemaker cluster within the SAP landscape. The High-availability cluster provider connects to Pacemaker, using ha_cluster_exporter endpoint, pulls telemetry data from the database and pushes it to Log Analytics workspace in the customer subscription. High-availability cluster provider collects data every 60 seconds from Pacemaker.

5.3.4.1 Installing HA Cluster Explorer

Install ha_cluster_exporter in each node within the Pacemaker cluster.

Clone the github repository to the machine

Use Zypper command to install the HA Cluster Explorer

Run the explorer in background so that data collection can be done

5.3.4.2 Adding HA Pacemaker Cluster to Azure Monitor

Configure a High-availability cluster provider for each node within the Pacemaker cluster.

Fill the following information and then click Create

• Name – A name for this provider. It should be unique for this Azure Monitor for SAP solutions instance.
• Prometheus Endpoint – http://<servername or ip address>:9664/metrics.
• SID – Use the SAP SID.
• Cluster name – The cluster name used when creating the cluster. The cluster name can be found in the cluster property cluster-name.
• Hostname – The Linux hostname of the VM.

Wait for the provider for creating a successful connection to Cluster

5.3.5 Configuring Microsoft SQL Server

We can configure one or more providers of provider type Microsoft SQL Server to enable data collection from SQL Server on Virtual Machines. SQL Server provider connects to Microsoft SQL Server over the SQL port, pulls telemetry data from the database, and pushes it to the Log Analytics workspace in the customer subscription. The SQL Server must be configured for SQL authentication and a SQL Server login, with the SAP DB as the default database for the provider, must be created. SQL Server provider collects data between every 60 seconds up to every hour from SQL server.

5.3.5.1 Creation of User

To connect to MSSQL server, a user must be created at the database level so that providers from Azure Monitor can connect to MSSQL Server using this user. User must have all the required authorizations and role to extract the required telemetry data.

We can run the below MS script in SQL Server Management Studio to create a user with the appropriate permissions needed to configure the provider

USE [<Database to monitor>]
DROP USER [<user name>]
GO
USE [master]
DROP USER [<user name>]
DROP LOGIN [<user name>]
GO
CREATE LOGIN [<user name>] WITH PASSWORD=N'<password>', DEFAULT_DATABASE=[<Database to monitor>], DEFAULT_LANGUAGE=[us_english], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
CREATE USER <user name> FOR LOGIN <user name>
ALTER ROLE [db_datareader] ADD MEMBER [<user name>]
ALTER ROLE [db_denydatawriter] ADD MEMBER [<user name>]
GRANT CONNECT TO <user name>
GRANT VIEW SERVER STATE TO <user name>
GRANT VIEW SERVER STATE TO <user name>
GRANT VIEW ANY DEFINITION TO <user name>
GRANT EXEC ON xp_readerrorlog TO <user name>
GO
USE [<Database to monitor>]
CREATE USER [<user name>] FOR LOGIN [<user name>]
ALTER ROLE [db_datareader] ADD MEMBER [<user name>]
ALTER ROLE [db_denydatawriter] ADD MEMBER [<user name>]
GO

5.3.5.2 Adding MSSQL Provider to Azure Monitor

After selecting the Add Provider we need to select Microsoft SQL Server from the drop-down menu. And then fill out all the requested details so that Provider can connect to MSSQL Server

Wait for the connection to be successful.

This is end of Part – II, in next part Monitoring of SAP Systems Using Azure Monitors – Part III of this article you can find more information about Dashboards, Workbooks and Displaying Graphs using Azure Monitors for SAP Solutions.