Merge pull request #222977 from DhruvSehgal/dhruvsehgal/update-steps-for-installing-ha-cluster-exporter

updated documantation for os, ha providers

Author: Stacyrch140

articles/virtual-machines/workloads/sap/configure-ha-cluster-azure-monitor-sap-solutions.md

@@ -5,7 +5,7 @@ author: MightySuz
 ms.service: virtual-machines-sap
 ms.subservice: baremetal-sap
 ms.topic: how-to
-ms.date: 10/19/2022
+ms.date: 01/05/2023
 ms.author: sujaj
 #Customer intent: As a developer, I want to create a High Availability Pacemaker cluster so I can use the resource with Azure Monitor for SAP solutions.
 ---
@@ -14,13 +14,13 @@ ms.author: sujaj
 
 [!INCLUDE [Azure Monitor for SAP solutions public preview notice](./includes/preview-azure-monitor.md)]
 
-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. 
+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
 
-- An Azure subscription. 
+- An Azure subscription.
 - An existing Azure Monitor for SAP solutions resource. To create an Azure Monitor for SAP solutions resource, see the [quickstart for the Azure portal](azure-monitor-sap-quickstart.md) or the [quickstart for PowerShell](azure-monitor-sap-quickstart-powershell.md).
 
 ## Install HA agent
@@ -33,28 +33,66 @@ For RHEL-based clusters, install **performance co-pilot (PCP)** and the **pcp-pm
 
 For RHEL-based pacemaker clusters, also install [PMProxy](https://access.redhat.com/articles/6139852) in each node.
 
+### Install HA Cluster Exporter on RHEL
+1. Install the required packages on the system.
+
+    ```bash
+    yum install pcp pcp-pmda-hacluster
+    ```
+
+1. Enable and start the required PCP Collector Services.
+
+    ```bash
+    systemctl enable pmcd
+    ```
+
+    ```bash
+    systemctl start pmcd
+    ```
+
+1. 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.
+
+    ```bash
+    cd $PCP_PMDAS_DIR/hacluster
+    ```
+
+    ```bash
+    . ./install
+    ```
+
+1. Enable and start the `pmproxy` service.
+
+    ```bash
+    sstemctl start pmproxy
+    ```
+
+    ```bash
+    systemctl enable pmproxy
+    ```
+
+1. 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.
 
 ## Create provider for Azure Monitor for SAP solutions
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-1. Go to the Azure Monitor for SAP solutions service. 
+1. Go to the Azure Monitor for SAP solutions service.
 1. Open your Azure Monitor for SAP solutions resource.
 1. In the resource's menu, under **Settings**, select **Providers**.
 1. 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.](./media/azure-monitor-sap/azure-monitor-providers-ha-cluster-start.png)  
+    ![Diagram of Azure Monitor for SAP solutions resource in the Azure portal, showing button to add a new provider.](./media/azure-monitor-sap/azure-monitor-providers-ha-cluster-start.png)
 
 1. For **Type**, select **High-availability cluster (Pacemaker)**.
-1. Configure providers for each node of the cluster by entering the endpoint URL for **HA Cluster Exporter Endpoint**. 
+1. 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`.
 
-    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.](./media/azure-monitor-sap/azure-monitor-providers-ha-cluster-suse.png)
 
-    ![Diagram of the setup for an Azure Monitor for SAP solutions resource, showing the fields for SUSE-based clusters.](./media/azure-monitor-sap/azure-monitor-providers-ha-cluster-suse.png)  
 
-    
     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.](./media/azure-monitor-sap/azure-monitor-providers-ha-cluster-rhel.png)  
+    ![Diagram of the setup for an Azure Monitor for SAP solutions resource, showing the fields for RHEL-based clusters.](./media/azure-monitor-sap/azure-monitor-providers-ha-cluster-rhel.png)
 
 
 1. 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.
@@ -67,6 +105,27 @@ For RHEL-based pacemaker clusters, also install [PMProxy](https://access.redhat.
 
 1. 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.
+
+    ```bash
+    sstemctl start pmproxy
+    ```
+
+1. Reenable the HA cluster exporter agent.
+    ```bash
+    systemctl enable pmproxy
+    ```
+
+1. Verify that the Prometheus endpoint is reachable from the subnet that provided while creating the Azure Monitor for SAP solutions resource.
+
 ## Next steps
 
 > [!div class="nextstepaction"]

articles/virtual-machines/workloads/sap/configure-linux-os-azure-monitor-sap-solutions.md

@@ -5,44 +5,72 @@ author: MightySuz
 ms.service: virtual-machines-sap
 ms.subservice: baremetal-sap
 ms.topic: how-to
-ms.date: 10/19/2022
+ms.date: 01/05/2023
 ms.author: sujaj
 #Customer intent: As a developer, I want to configure a Linux provider so that I can use Azure Monitor for SAP solutions for monitoring.
 ---
 # Configure Linux provider for Azure Monitor for SAP solutions (preview)
 
 [!INCLUDE [Azure Monitor for SAP solutions public preview notice](./includes/preview-azure-monitor.md)]
 
-In this how-to guide, you'll learn to create a Linux OS provider for *Azure Monitor for SAP solutions* resources. 
+In this how-to guide, you'll learn to create a Linux OS provider for *Azure Monitor for SAP solutions* resources.
 
 This content applies to both versions of the service, *Azure Monitor for SAP solutions* and *Azure Monitor for SAP solutions (classic)*.
 
 ## Prerequisites
 
-- An Azure subscription. 
+- An Azure subscription.
 - An existing Azure Monitor for SAP solutions resource. To create an Azure Monitor for SAP solutions resource, see the [quickstart for the Azure portal](azure-monitor-sap-quickstart.md) or the [quickstart for PowerShell](azure-monitor-sap-quickstart-powershell.md).
-- Install [node exporter version 1.3.0](https://prometheus.io/download/#node_exporter) in each SAP host that you want to monitor, either BareMetal or Azure virtual machine (Azure VM). For more information, see [the node exporter GitHub repository](https://github.com/prometheus/node_exporter).    
+- Install the [node exporter version 1.3.0](https://prometheus.io/download/#node_exporter) in each SAP host that you want to monitor, either BareMetal or Azure virtual machine (Azure VM). For more information, see [the node exporter GitHub repository](https://github.com/prometheus/node_exporter).
 
-## Create Linux provider
+To install the node exporter on Linux:
+
+1. Run `wget https://github.com/prometheus/node_exporter/releases/download/v*/node_exporter-*.*-amd64.tar.gz`. Replace `*` with the version number.
+
+1. Run `tar xvfz node_exporter-*.*-amd64.tar.gz`
+
+1. Run `cd node_exporter-*.*-amd64`
+
+1. Run `./node_exporter`
+
+1. The node exporter now starts collecting data. You can export the data at `http://IP:9100/metrics`.
+
+## Create Linux OS provider
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. Go to the Azure Monitor for SAP solutions or Azure Monitor for SAP solutions (classic) service.
 1. Select **Create** to make a new Azure Monitor for SAP solutions resource.
 1. Select **Add provider**.
 1. Configure the following settings for the new provider:
     1. For **Type**, select **OS (Linux)**.
-    1. For **Name**, enter a name that will be the identifier for the BareMetal instance.         
-    1. For **Node Exporter Endpoint**, enter `http://IP:9100/metrics`.    
+    1. For **Name**, enter a name that will be the identifier for the BareMetal instance.
+    1. For **Node Exporter Endpoint**, enter `http://IP:9100/metrics`.
     1. For the IP address, use the private IP address of the Linux host. Make sure the host and Azure Monitor for SAP solutions resource are in the same virtual network.
-1. Open firewall port 9100 on the Linux host. 
-     1. If you're using `firewall-cmd`, run `_firewall-cmd_ _--permanent_ _--add-port=9100/tcp_ ` then `_firewall-cmd_ _--reload_`.
-     1. If you're using `ufw`, run `_ufw_ _allow_ _9100/tcp_` then `_ufw_ _reload_`.
-1. If the Linux host is an Azure virtual machine (VM), make sure that all applicable network security groups (NSGs) allow inbound traffic at port 9100 from **VirtualNetwork** as the source.         
-1. Select **Add provider** to save your changes. 
+1. Open firewall port 9100 on the Linux host.
+    1. If you're using `firewall-cmd`, run `_firewall-cmd_ _--permanent_ _--add-port=9100/tcp_ ` then `_firewall-cmd_ _--reload_`.
+    1. If you're using `ufw`, run `_ufw_ _allow_ _9100/tcp_` then `_ufw_ _reload_`.
+1. If the Linux host is an Azure virtual machine (VM), make sure that all applicable network security groups (NSGs) allow inbound traffic at port 9100 from **VirtualNetwork** as the source.
+1. Select **Add provider** to save your changes.
 1. Continue to add more providers as needed.
 1. Select **Review + create** to review the settings.
 1. Select **Create** to finish creating the resource.
 
+## Troubleshooting
+
+Use these steps to resolve common errors.
+
+### Unable to reach the Prometheus endpoint
+
+When the provider settings validation operation fails with the code ‘PrometheusURLConnectionFailure’:
+
+1. Open firewall port 9100 on the Linux host.
+    1. If you're using `firewall-cmd`, run `_firewall-cmd_ _--permanent_ _--add-port=9100/tcp_ ` then `_firewall-cmd_ _--reload_`.
+    1. If you're using `ufw`, run `_ufw_ _allow_ _9100/tcp_` then `_ufw_ _reload_`.
+1. Try to restart the node exporter agent:
+    1. Go to the folder where you installed the node exporter (the file name resembles `node_exporter-*.*-amd64`).
+    1. Run `./node_exporter`.
+1. Verify that the Prometheus endpoint is reachable from the subnet that you provided while creating the Azure Monitor for SAP solutions resource.
+
 ## Next steps
 
 > [!div class="nextstepaction"]