Azure Monitor for SAP Solutions FAQ (preview)

Frequently asked questions

This article provides answers to frequently asked questions (FAQ) about Azure Monitor for SAP Solutions.

Do I have to pay for Azure Monitor for SAP Solutions?

There's no licensing fee for Azure Monitor for SAP Solutions. However, you're responsible for the cost of managed resource group components.

In which regions is this service available for public preview?

For public preview, this service will be available in East US 2, West US 2, East US, and West Europe.

Do I need to give permissions to allow the deployment of a managed resource group in my subscription?

No, explicit permissions aren't required.

Where does the collector virtual machine (VM) reside?

When deploying Azure Monitor for SAP Solutions, we recommend you choose the same VNET for your monitoring resource as your SAP HANA server. So we recommend the collector VM be in the same VNET as the SAP HANA server. If you're using a non-HANA database, the collector VM will be in the same VNET as the non-HANA database.

Which versions of HANA are supported?

HANA 1.0 SPS 12 (Rev. 120 or higher) and HANA 2.0 SPS03 or higher are supported.

Which HANA deployment configurations are supported?

The following configurations are supported:

  • Single node (scale-up) and multi-node (scale-out).
  • Single database container (HANA 1.0 SPS 12) and multiple database containers (HANA 1.0 SPS 12 or HANA 2.0).
  • Auto host failover (n+1) and HSR.

Which SQL Server Versions are supported?

SQL Server 2012 SP4 or higher.

Which SQL Server configurations are supported?

The following configurations are supported:

  • Default or named standalone instances in a virtual machine.
  • Clustered instances or instances in an AlwaysOn configuration when either using the virtual name of the clustered resource or the AlwaysOn listener name.
  • Currently, no cluster or AlwaysOn specific metrics are collected.
  • Azure SQL Database (PAAS) is currently not supported.

What happens if I accidentally delete the managed resource group?

The managed resource group is locked by default. So the chances of accidentally deleting the managed resource group are minuscule. If you do delete the managed resource group, Azure Monitor for SAP Solutions will stop working. You'll have to deploy a new Azure Monitor for SAP Solutions resource and start over.

Which roles do I need in my Azure subscription to deploy Azure Monitor for SAP Solutions resource?

Contributor role.

What is the SLA on this product?

Previews are excluded from service level agreements. Read the full license term through Azure Monitor for SAP Solutions marketplace image.

Can I monitor my entire landscape through this solution?

In public preview, you can currently monitor:

  • HANA database
  • The underlying infrastructure
  • The High-availability cluster
  • Microsoft SQL server
  • SAP Netweaver availability
  • SAP Application Instance availability metrics

Does this service replace SAP Solution manager?

No. Customers can still use SAP Solution manager for Business process monitoring.

What is the value of this service over traditional solutions like SAP HANA Cockpit/Studio?

Azure Monitor for SAP Solutions isn't HANA database specific. Azure Monitor for SAP Solutions supports also AnyDB.

Which SAP NetWeaver versions are supported?

SAP NetWeaver 7.0 or higher.

Which SAP NetWeaver configurations are supported?

Supports ABAP, Java, and dual-stack SAP NetWeaver Application Server configurations.

Why do I need to unprotect methods for SAP NetWeaver application monitoring?

In SAP releases >= 7.3, most web service methods are protected by default. To fetch availability and performance metrics by calling these methods, you need to unprotect the following methods: GetQueueStatistic, ABAPGetWPTable, GetProcessList, EnqGetStatistic, and GetSystemInstancelist.

Is there any risk in unprotecting SAPCONTROL web methods?

In general, you can unprotect SAPCONTROL web methods without posing a security risk as such. You can restrict access to unprotected web methods via server ports 5XX13 / 5XX14 of sapstartsrv. You do so by adding a filter in the SAP Access Control List. The OSS note describes the required configuration.

Do I need to restart my SAP instances after performing system configurations for setting up SAP NetWeaver provider?

Yes, once you have unprotected methods through SAP config changes, you'll need to restart the respective SAP systems to ensure the configuration changes are updated.

Next steps

Learn more about Azure Monitor for SAP Solutions.