Freshness

Xelu86 · Xelu86 · commit 6cf6bb58f5b8 · 2026-03-13T14:39:35.000-04:00
diff --git a/articles/sap/monitor/providers.md b/articles/sap/monitor/providers.md
@@ -1,12 +1,12 @@
 ---
 title: What are providers in Azure Monitor for SAP solutions?
-description: This article provides answers to frequently asked questions about Azure Monitor for SAP solutions providers.
-author: rdeltcheva
+description: Discover answers to frequently asked questions about Azure Monitor for SAP solutions providers.
 ms.service: sap-on-azure
 ms.subservice: sap-monitor
 ms.topic: concept-article
-ms.date: 08/22/2024
+author: rdeltcheva
 ms.author: radeltch
+ms.date: 03/13/2026
 ms.custom:
   - linux-related-content
   - sfi-image-nochange
@@ -22,13 +22,15 @@ You can choose to configure different provider types for data collection from th
 
 You can also configure multiple providers of a specific provider type to reuse the same SAP monitor resource and associated managed group. For more information, see [Manage Azure Resource Manager resource groups by using the Azure portal](../../azure-resource-manager/management/manage-resource-groups-portal.md).
 
-![Diagram that shows Azure Monitor for SAP solutions connection to available providers.](./media/providers/providers.png)
+![A diagram that shows Azure Monitor for SAP solutions connection to available providers.](./media/providers/providers.png)
 
 We recommend that you configure at least one provider when you deploy an Azure Monitor for SAP solutions resource. By configuring a provider, you start data collection from the corresponding component for which the provider is configured.
 
 If you don't configure any providers at the time of deployment, the Azure Monitor for SAP solutions resource is still deployed, but no data is collected. You can add providers after deployment through the SAP monitor resource in the Azure portal. You can add or delete providers from the SAP monitor resource at any time.
 
-## Provider type: SAP NetWeaver
+## Provider types
+
+# [SAP NetWeaver](#tab/sap-netweaver)
 
 You can configure one or more providers of the provider type SAP NetWeaver to enable data collection from the SAP NetWeaver layer. The Azure Monitor for SAP solutions NetWeaver provider uses the existing:
 
@@ -37,40 +39,42 @@ You can configure one or more providers of the provider type SAP NetWeaver to en
 
 With the SAP NetWeaver provider, you can get the:
 
-- SAP system and application server availability, for example, instance process availability of Dispatcher, ICM, Gateway, Message Server, Enqueue Server, and IGS Watchdog (SAPOsControl).
+- SAP system and application server availability. For example, instance process availability of Dispatcher, ICM, Gateway, Message Server, Enqueue Server, and IGS Watchdog (SAPOsControl).
 - Work process usage statistics and trends (SAPOsControl).
 - Enqueue lock statistics and trends (SAPOsControl).
 - Queue usage statistics and trends (SAPOsControl).
-- SMON metrics (**Tcode - /SDF/SMON**) (RFC).
-- SWNC workload, memory, transaction, user, RFC usage (**Tcode - St03n**) (RFC).
-- Short dumps (**Tcode - ST22**) (RFC).
-- Object lock (**Tcode - SM12**) (RFC).
-- Failed updates (**Tcode - SM13**) (RFC).
-- System logs analysis (**Tcode - SM21**) (RFC).
-- Batch jobs statistics (**Tcode - SM37**) (RFC).
-- Outbound queues (**Tcode - SMQ1**) (RFC).
-- Inbound queues (**Tcode - SMQ2**) (RFC).
-- Transactional RFC (**Tcode - SM59**) (RFC).
-- STMS Change Transport System metrics (**Tcode - STMS**) (RFC).
+- SMON metrics (`Tcode` - **/SDF/SMON**) (RFC).
+- SWNC workload, memory, transaction, user, RFC usage (`Tcode` - **St03n**) (RFC).
+- Short dumps (`Tcode` - **ST22**) (RFC).
+- Object lock (`Tcode` - **SM12**) (RFC).
+- Failed updates (`Tcode` - **SM13**) (RFC).
+- System logs analysis (`Tcode` - **SM21**) (RFC).
+- Batch jobs statistics (`Tcode` - **SM37**) (RFC).
+- Outbound queues (`Tcode` - **SMQ1**) (RFC).
+- Inbound queues (`Tcode` - **SMQ2**) (RFC).
+- Transactional RFC (`Tcode` - **SM59**) (RFC).
+- STMS Change Transport System metrics (`Tcode` - ***STMS**) (RFC).
 
 Configuring the SAP NetWeaver provider requires:
 
 For SOAP web methods:
-   - Fully qualified domain name (FQDN) of the SAP Web Dispatcher or the SAP application server.
-   - SAP system ID, Instance no.
-   - Host file entries of all SAP application servers that get listed via the SAPcontrol `GetSystemInstanceList` web method.
+
+- Fully qualified domain name (FQDN) of the SAP Web Dispatcher or the SAP application server.
+- SAP system ID, Instance no.
+- Host file entries of all SAP application servers that get listed via the SAPcontrol `GetSystemInstanceList` web method.
 
 For SOAP+RFC:
-   - FQDN of the SAP Web Dispatcher or the SAP application server.
-   - SAP system ID, Instance no.
-   - SAP client ID, HTTP port, and SAP username and password for sign in.
-   - Host file entries of all SAP application servers that get listed via the SAPcontrol `GetSystemInstanceList` web method.
+
+- FQDN of the SAP Web Dispatcher or the SAP application server.
+- SAP system ID, Instance no.
+- SAP client ID, HTTP port, and SAP username and password for sign in.
+- Host file entries of all SAP application servers that get listed via the SAPcontrol `GetSystemInstanceList` web method.
 
 For more information, see [Configure SAP NetWeaver for Azure Monitor for SAP solutions](provider-netweaver.md).
 
-![Diagram that shows the NetWeaver provider architecture.](./media/providers/netweaver-architecture.png)
+![A diagram that shows Azure Monitor for SAP solutions with three providers for the SAP NetWeaver architecture.](./media/providers/netweaver-architecture.png)
 
-## Provider type: SAP HANA
+# [SAP HANA](#tab/sap-hana)
 
 You can configure one or more providers of the provider type **SAP HANA** to enable data collection from the SAP HANA database. The SAP HANA provider connects to the SAP HANA database over the SQL port. The provider pulls data from the database and pushes it to the Log Analytics workspace in your subscription. The SAP HANA provider collects data every minute from the SAP HANA database.
 
@@ -92,6 +96,7 @@ With the SAP HANA provider, you can see the:
 - SAP HANA blocking transactions.
 
 Configuring the SAP HANA provider requires the:
+
 - Host IP address.
 - HANA SQL port number.
 - SYSTEMDB username and password.
@@ -100,41 +105,43 @@ We recommend that you configure the SAP HANA provider against SYSTEMDB. However,
 
 For more information, see [Configure SAP HANA provider for Azure Monitor for SAP solutions](provider-hana.md).
 
-![Diagram that shows Azure Monitor for SAP solutions providers - SAP HANA architecture.](./media/providers/azure-monitor-providers-hana.png)
+![A diagram that shows Azure Monitor for SAP solutions with three providers for the SAP HANA architecture.](./media/providers/azure-monitor-providers-hana.png)
 
-## Provider type: SQL Server
+# [SQL Server](#tab/sql-server)
 
 You can configure one or more SQL Server providers to enable data collection from [SQL Server on virtual machines](https://azure.microsoft.com/services/virtual-machines/sql-server/). The SQL Server provider connects to SQL Server over the SQL port. It then pulls data from the database and pushes it to the Log Analytics workspace in your subscription. Configure SQL Server for SQL authentication and for signing in with the SQL Server username and password. Set the SAP database as the default database for the provider. The SQL Server provider collects data every 60 seconds up to every hour from the SQL Server.
 
 With the SQL Server provider, you can get the:
+
 - Underlying infrastructure usage.
 - Top SQL statements.
 - Top largest table.
 - Problems recorded in the SQL Server error log.
 - Blocking processes and others.
 
 Configuring SQL Server provider requires the:
+
 - SAP system ID.
 - Host IP address.
 - SQL Server port number.
 - SQL Server username and password.
 
- For more information, see [Configure SQL Server for Azure Monitor for SAP solutions](provider-sql-server.md).
+For more information, see [Configure SQL Server for Azure Monitor for SAP solutions](provider-sql-server.md).
 
-![Diagram that shows Azure Monitor for SAP solutions providers - SQL architecture.](./media/providers/azure-monitor-providers-sql.png)
+![A diagram that shows Azure Monitor for SAP solutions with three providers for the SQL server architecture.](./media/providers/azure-monitor-providers-sql.png)
 
-## Provider type: High-availability cluster
+# [High-availability cluster](#tab/ha-cluster)
 
 You can configure one or more providers of the provider type *high-availability cluster* to enable data collection from the Pacemaker cluster within the SAP landscape. The high-availability cluster provider connects to Pacemaker by using the [ha_cluster_exporter](https://github.com/ClusterLabs/ha_cluster_exporter) for **SUSE**-based clusters and by using [Performance copilot](https://access.redhat.com/articles/6139852) for **RHEL**-based clusters. Azure Monitor for SAP solutions then pulls data from the cluster and pushes it to the Log Analytics workspace in your subscription. The high-availability cluster provider collects data every 60 seconds from Pacemaker.
 
 With the high-availability cluster provider, you can get the:
 
- - Cluster status represented as a roll-up of node and resource status.
- - Location constraints.
- - Trends.
- - [Others](https://github.com/ClusterLabs/ha_cluster_exporter/blob/master/doc/metrics.md).
+- Cluster status represented as a roll-up of node and resource status.
+- Location constraints.
+- Trends.
+- [Others](https://github.com/ClusterLabs/ha_cluster_exporter/blob/master/doc/metrics.md).
 
-![Diagram that shows Azure Monitor for SAP solutions providers - High-availability cluster architecture.](./media/providers/azure-monitor-providers-pacemaker-cluster.png)
+![A diagram that shows Azure Monitor for SAP solutions with three providers for the High-availability cluster architecture.](./media/providers/azure-monitor-providers-pacemaker-cluster.png)
 
 To configure a high-availability cluster provider, two primary steps are involved:
 
@@ -155,39 +162,39 @@ To configure a high-availability cluster provider, two primary steps are involve
    - **Cluster name**: The cluster name used when you're creating the cluster. You can find the cluster name in the cluster property `cluster-name`.
    - **Hostname**: The Linux hostname of the virtual machine (VM).
 
-  For more information, see [Create a high-availability cluster provider for Azure Monitor for SAP solutions](provider-ha-pacemaker-cluster.md).
+   For more information, see [Create a high-availability cluster provider for Azure Monitor for SAP solutions](provider-ha-pacemaker-cluster.md).
 
-## Provider type: OS (Linux)
+# [OS Linux](#tab/os-linux)
 
 You can configure one or more providers of the provider type OS (Linux) to enable data collection from a BareMetal or VM node. The OS (Linux) provider connects to BareMetal or VM nodes by using the [Node_Exporter](https://github.com/prometheus/node_exporter) endpoint. It then pulls data from the nodes and pushes it to the Log Analytics workspace in your subscription. The OS (Linux) provider collects data every 60 seconds for most of the metrics from the nodes.
 
 With the OS (Linux) provider, you can get the:
 
-   - CPU usage and CPU usage by process.
-   - Disk usage and I/O read and write.
-   - Memory distribution, memory usage, and swap memory usage.
-   - Network usage and the network inbound and outbound traffic details.
+- CPU usage and CPU usage by process.
+- Disk usage and I/O read and write.
+- Memory distribution, memory usage, and swap memory usage.
+- Network usage and the network inbound and 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 node.
-   You have two options for installing [Node_Exporter](https://github.com/prometheus/node_exporter):
-      - For automated installation with Ansible, use [Node_Exporter](https://github.com/prometheus/node_exporter) on each BareMetal or VM node to install the OS (Linux) provider.
-      - Do a [manual installation](https://prometheus.io/docs/guides/node-exporter/).
+1. Install [Node_Exporter](https://github.com/prometheus/node_exporter) on each BareMetal or VM node. You have two options for installing [Node_Exporter](https://github.com/prometheus/node_exporter):
+
+   - For automated installation with Ansible, use [Node_Exporter](https://github.com/prometheus/node_exporter) on each BareMetal or VM node to install the OS (Linux) provider.
+   - Do a [manual installation](https://prometheus.io/docs/guides/node-exporter/).
+
+1. Configure an OS (Linux) provider for each BareMetal or VM node instance in your environment. To configure the OS (Linux) provider, the following information is required:
 
-1. Configure an 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 that's unique to the Azure Monitor for SAP solutions instance.
-      - **Node Exporter endpoint**: Usually `http://<servername or ip address>:9100/metrics`.
+   - **Name**: A name for this provider that's unique to the Azure Monitor for SAP solutions instance.
+   - **Node Exporter endpoint**: Usually `http://<servername or ip address>:9100/metrics`.
 
 Port 9100 is exposed for the `Node_Exporter` endpoint.
 
 For more information, see [Configure Linux provider for Azure Monitor for SAP solutions](provider-linux.md).
 
-> [!Warning]
+> [!WARNING]
 > Make sure `Node-Exporter` keeps running after the node reboot.
 
-## Provider type: IBM Db2
+# [IBM Db2](#tab/ibm-db2)
 
 You can configure one or more IBM Db2 providers to enable data collection from IBM Db2 servers. The Db2 Server provider connects to the database over a specific port. It then pulls data from the database and pushes it to the Log Analytics workspace in your subscription. The Db2 Server provider collects data every 60 seconds up to every hour from the Db2 Server.
 
@@ -200,6 +207,7 @@ With the IBM Db2 provider, you can get the:
 - Top 20 runtime and executions.
 
 Configuring the IBM Db2 provider requires the:
+
 - SAP system ID.
 - Host IP address.
 - Database name.
@@ -208,7 +216,9 @@ Configuring the IBM Db2 provider requires the:
 
 For more information, see [Create IBM Db2 provider for Azure Monitor for SAP solutions](provider-ibm-db2.md).
 
-![Diagram that shows Azure Monitor for SAP solutions providers - IBM Db2 architecture.](./media/providers/azure-monitor-providers-db2.png)
+![A diagram that shows Azure Monitor for SAP solutions with three providers for the IBM Db2 architecture.](./media/providers/azure-monitor-providers-db2.png)
+
+---
 
 ## Next steps
 
