Merge pull request #142909 from NitVijay/patch-4

Update azure-monitor-providers.md

Author: v-andreaco

articles/virtual-machines/workloads/sap/azure-monitor-providers.md

@@ -39,7 +39,7 @@ If customers don't configure any providers at the time of deploying SAP monitor
 Customers 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 customer subscription. The SAP HANA provider collects data every 1 minute from the SAP HANA database.  
 
 In public preview, customers can expect to see the following data with SAP HANA provider: Underlying infrastructure utilization, SAP HANA Host status, SAP HANA System Replication, and SAP HANA Backup telemetry data. 
-To configure SAP HANA provider, Host IP address, HANA SQL port number, and SYSTEMDB username and password are required. Customers are recommended to configure SAP HANA provider against SYSTEMDB, however additional providers can be configured against other database tenants.
+To configure SAP HANA provider, Host IP address, HANA SQL port number, and SYSTEMDB username and password are required. Customers are recommended to configure SAP HANA provider against SYSTEMDB, however more providers can be configured against other database tenants.
 
 ![Azure Monitor for SAP solutions providers - SAP HANA](./media/azure-monitor-sap/azure-monitor-providers-hana.png)
 
@@ -66,18 +66,46 @@ To configure a High-availability cluster provider, two primary steps are involve
    To configure the High-availability cluster provider, the following information is required:
 
    - **Name**. A name for this provider. It should be unique for this Azure Monitor for SAP solutions instance.
-   - **Prometheus Endpoint**. Usually http\://\<servername or ip address\>:9664/metrics.
+   - **Prometheus Endpoint**. http\://\<servername or ip address\>:9664/metrics.
    - **SID**. For SAP systems, use the SAP SID. For other systems (for example, NFS clusters), use a three-character name for the cluster. The SID must be distinct from other clusters that are monitored.   
    - **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.  
 
+
+## Provider type OS (Linux)
+Customers 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](https://github.com/prometheus/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. 
+
+In Public preview, customers can expect to see the following data with OS (Linux) provider: 
+   - CPU Usage, CPU Usage by Process 
+   - Disk Utilization, I/O Read & Write 
+   - Memory Distribution, Memory Usage, Swap Memory Usage 
+   - Network Usage, Network Inbound & outbound Traffic Details. 
+
+To configure an OS (Linux) provider, two primary steps are involved:
+1. Install [Node_Exporter](https://github.com/prometheus/node_exporter) on each BareMetal or VM Nodes.
+   You have two options for installing [Node_exporter](https://github.com/prometheus/node_exporter): 
+      - For Automation installation with Ansible use [Node_Exporter](https://github.com/prometheus/node_exporter) on each BareMetal or VM Nodes to install OS (Linux) Provider.  
+      - Do a [manual installation](https://prometheus.io/docs/guides/node-exporter/).
+
+2. Configure a OS (Linux) Provider for each BareMetal or VM Node Instance in your environment. 
+   To configure the OS (Linux) Provider, the following information is required: 
+      - Name. A name for this provider. It should be unique for this Azure Monitor for SAP solutions instance. 
+      - Node Exporter Endpoint. Usually http://<servername or ip address>:9100/metrics 
+
+> [!NOTE]
+> 9100 is a Port Exposed for Node_Exporter Endpoint.
+
+> [!Warning]
+> Ensure Node Exporter keeps running after node reboot. 
+
+
 ## Provider type Microsoft SQL server
 
 Customers can configure one or more providers of provider type *Microsoft SQL Server* to enable data collection from [SQL Server on Virtual Machines](https://azure.microsoft.com/services/virtual-machines/sql-server/). 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.  
 
 In public preview, customers can expect to see the following data with SQL Server provider: underlying infrastructure utilization, top SQL statements, top largest table, problems recorded in the SQL Server error logs, blocking processes and others.  
 
-To configure Microsoft SQL Server provider, the SAP System ID, the Host IP address, SQL Server port number as well as the SQL Server login name and password are required.
+To configure Microsoft SQL Server provider, the SAP System ID, the Host IP address, SQL Server port number and the SQL Server login name and password are required.
 
 ![Azure Monitor for SAP solutions providers - SQL](./media/azure-monitor-sap/azure-monitor-providers-sql.png)