Create High Availability cluster provider for Azure Monitor for SAP solutions (preview)

Important

Azure Monitor for SAP solutions is currently in PREVIEW. See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.

In this how-to guide, you'll learn to create a High Availability (HA) Pacemaker cluster provider for Azure Monitor for SAP solutions. You'll install the HA agent, then create the provider for Azure Monitor for SAP solutions.

This content applies to both Azure Monitor for SAP solutions and Azure Monitor for SAP solutions (classic) versions.

Prerequisites

Install HA agent

Before adding providers for HA (Pacemaker) clusters, install the appropriate agent for your environment in each cluster node.

For SUSE-based clusters, install ha_cluster_provider in each node. For more information, see the HA cluster exporter installation guide. Supported SUSE versions include SLES for SAP 12 SP3 and above.

For RHEL-based clusters, install performance co-pilot (PCP) and the pcp-pmda-hacluster sub package in each node.For more information, see the PCP HACLUSTER agent installation guide. Supported RHEL versions include 8.2, 8.4 and above.

For RHEL-based pacemaker clusters, also install PMProxy in each node.

Install HA Cluster Exporter on RHEL

  1. Install the required packages on the system.

    yum install pcp pcp-pmda-hacluster
    
  2. Enable and start the required PCP Collector Services.

    systemctl enable pmcd
    
    systemctl start pmcd
    
  3. Install and enable the HA Cluster PMDA. Replace $PCP_PMDAS_DIR with the path where hacluster is installed. Use the find command in Linuxto find the path.

    cd $PCP_PMDAS_DIR/hacluster
    
    . ./install
    
  4. Enable and start the pmproxy service.

    sstemctl start pmproxy
    
    systemctl enable pmproxy
    
  5. Data will then be collected by PCP on the system. You can export the data using pmproxy at http://<SERVER-NAME-OR-IP-ADDRESS>:44322/metrics?names=ha_cluster. Replace <SERVER-NAME-OR-IP-ADDRESS> with your server name or IP address.

Prerequisites to enable secure communication

To enable TLS 1.2 or higher, follow the steps mentioned here

Create provider for Azure Monitor for SAP solutions

  1. Sign in to the Azure portal.

  2. Go to the Azure Monitor for SAP solutions service.

  3. Open your Azure Monitor for SAP solutions resource.

  4. In the resource's menu, under Settings, select Providers.

  5. Select Add to add a new provider.

    Diagram of Azure Monitor for SAP solutions resource in the Azure portal, showing button to add a new provider.

  6. For Type, select High-availability cluster (Pacemaker).

  7. Optional Select Enable secure communciation, choose a certificate type

  8. Configure providers for each node of the cluster by entering the endpoint URL for HA Cluster Exporter Endpoint.

    1. For SUSE-based clusters, enter http://<IP-address> :9664/metrics.

    Diagram of the setup for an Azure Monitor for SAP solutions resource, showing the fields for SUSE-based clusters.

    1. For RHEL-based clusters, enter http://<'IP address'>:44322/metrics?names=ha_cluster.

    Diagram of the setup for an Azure Monitor for SAP solutions resource, showing the fields for RHEL-based clusters.

  9. Enter the system identifiers, host names, and cluster names. For the system identifier, enter a unique SAP system identifier for each cluster. For the hostname, the value refers to an actual hostname in the VM. Use hostname -s for SUSE- and RHEL-based clusters.

  10. Select Add provider to save.

  11. Continue to add more providers as needed.

  12. Select Review + create to review the settings.

  13. Select Create to finish creating the resource.

Troubleshooting

Use the following troubleshooting steps for common errors.

Unable to reach the Prometheus endpoint

When the provider settings validation operation fails with the code ‘PrometheusURLConnectionFailure’:

  1. Restart the HA cluster exporter agent.

    sstemctl start pmproxy
    
  2. Reenable the HA cluster exporter agent.

    systemctl enable pmproxy
    
  3. Verify that the Prometheus endpoint is reachable from the subnet that provided while creating the Azure Monitor for SAP solutions resource.

Next steps