Skip to content

Commit 8347078

Browse files
ShawnJacksonShawnJackson
authored
Merge pull request #241260 from paulth1/sap-monitor-batch-2
[AQ] edit pass: Sap monitor batch 2
2 parents 84b8f02 + 7464fb2 commit 8347078

File tree

5 files changed

+103
-100
lines changed

5 files changed

+103
-100
lines changed

‎articles/sap/monitor/provider-ha-pacemaker-cluster.md

Lines changed: 22 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,35 +1,36 @@
11
---
22
title: Create a High Availability Pacemaker cluster provider for Azure Monitor for SAP solutions
3-
description: Learn how to configure High Availability (HA) Pacemaker cluster providers for Azure Monitor for SAP solutions.
3+
description: Learn how to configure high-availability (HA) Pacemaker cluster providers for Azure Monitor for SAP solutions.
44
author: MightySuz
55
ms.service: sap-on-azure
66
ms.subservice: sap-monitor
77
ms.topic: how-to
88
ms.date: 01/05/2023
99
ms.author: sujaj
10-
#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.
10+
#Customer intent: As a developer, I want to create a high-availability Pacemaker cluster so that I can use the resource with Azure Monitor for SAP solutions.
1111
---
1212

13-
# Create High Availability cluster provider for Azure Monitor for SAP solutions
13+
# Create high-availability cluster provider for Azure Monitor for SAP solutions
1414

15-
In this how-to guide, you learn to create a High Availability (HA) Pacemaker cluster provider for Azure Monitor for SAP solutions. You install the HA agent, then create the provider for Azure Monitor for SAP solutions.
15+
In this how-to guide, you learn how to create a high-availability (HA) Pacemaker cluster provider for Azure Monitor for SAP solutions. You install the HA agent and then create the provider for Azure Monitor for SAP solutions.
1616

1717
## Prerequisites
1818

1919
- An Azure subscription.
2020
- An existing Azure Monitor for SAP solutions resource. To create an Azure Monitor for SAP solutions resource, see the [quickstart for the Azure portal](quickstart-portal.md) or the [quickstart for PowerShell](quickstart-powershell.md).
2121

22-
## Install HA agent
22+
## Install an HA agent
2323

24-
Before adding providers for HA (Pacemaker) clusters, install the appropriate agent for your environment in each cluster node.
24+
Before you add providers for HA (Pacemaker) clusters, install the appropriate agent for your environment in each cluster node.
2525

26-
For SUSE-based clusters, install **ha_cluster_provider** in each node. For more information, see [the HA cluster exporter installation guide](https://github.com/ClusterLabs/ha_cluster_exporter#installation). Supported SUSE versions include SLES for SAP 12 SP3 and later versions.
26+
For SUSE-based clusters, install **ha_cluster_provider** in each node. For more information, see the [HA cluster exporter installation guide](https://github.com/ClusterLabs/ha_cluster_exporter#installation). Supported SUSE versions include SLES for SAP 12 SP3 and later versions.
2727

28-
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](https://access.redhat.com/articles/6139852). Supported RHEL versions include 8.2, 8.4 and later versions.
28+
For RHEL-based clusters, install **performance co-pilot (PCP)** and the **pcp-pmda-hacluster** subpackage in each node. For more information, see the [PCP HACLUSTER agent installation guide](https://access.redhat.com/articles/6139852). Supported RHEL versions include 8.2, 8.4, and later versions.
2929

30-
For RHEL-based pacemaker clusters, also install [PMProxy](https://access.redhat.com/articles/6139852) in each node.
30+
For RHEL-based Pacemaker clusters, also install [PMProxy](https://access.redhat.com/articles/6139852) in each node.
31+
32+
### Install an HA cluster exporter on RHEL
3133

32-
### Install HA Cluster Exporter on RHEL
3334
1. Install the required packages on the system.
3435

3536
```bash
@@ -46,7 +47,7 @@ For RHEL-based pacemaker clusters, also install [PMProxy](https://access.redhat.
4647
systemctl start pmcd
4748
```
4849

49-
1. Install and enable the HA Cluster PMDA. Replace `$PCP_PMDAS_DIR` with the path where `hacluster` is installed. Use the `find` command in Linux to find the path.
50+
1. Install and enable the HA cluster PMDA. Replace `$PCP_PMDAS_DIR` with the path where `hacluster` is installed. Use the `find` command in Linux to find the path.
5051

5152
```bash
5253
cd $PCP_PMDAS_DIR/hacluster
@@ -66,33 +67,33 @@ For RHEL-based pacemaker clusters, also install [PMProxy](https://access.redhat.
6667
systemctl start pmproxy
6768
```
6869

69-
1. Data will then be collected in the system by PCP. 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.
70+
1. Data is then collected in the system by PCP. You can export the data by 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.
7071

7172
## Prerequisites to enable secure communication
7273

73-
To [enable TLS 1.2 or higher](enable-tls-azure-monitor-sap-solutions.md), follow the steps [mentioned here](https://github.com/ClusterLabs/ha_cluster_exporter#tls-and-basic-authentication)
74+
To [enable TLS 1.2 or higher](enable-tls-azure-monitor-sap-solutions.md), follow the steps in [this article](https://github.com/ClusterLabs/ha_cluster_exporter#tls-and-basic-authentication).
7475

75-
## Create provider for Azure Monitor for SAP solutions
76+
## Create a provider for Azure Monitor for SAP solutions
7677

7778
1. Sign in to the [Azure portal](https://portal.azure.com).
7879
1. Go to the Azure Monitor for SAP solutions service.
7980
1. Open your Azure Monitor for SAP solutions resource.
80-
1. In the resource's menu, under **Settings**, select **Providers**.
81+
1. On the resource's menu, under **Settings**, select **Providers**.
8182
1. Select **Add** to add a new provider.
8283
83-
![Diagram of Azure Monitor for SAP solutions resource in the Azure portal, showing button to add a new provider.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-start.png)
84+
![Diagram that shows Azure Monitor for SAP solutions resource in the Azure portal, showing button to add a new provider.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-start.png)
8485
8586
1. For **Type**, select **High-availability cluster (Pacemaker)**.
86-
1. *Optional* Select **Enable secure communication**, choose a certificate type
87+
1. (Optional) Select **Enable secure communication** and choose a certificate type.
8788
1. Configure providers for each node of the cluster by entering the endpoint URL for **HA Cluster Exporter Endpoint**.
8889
8990
1. For SUSE-based clusters, enter `http://<IP-address>:9664/metrics`.
9091
91-
![Diagram of the setup for an Azure Monitor for SAP solutions resource, showing the fields for SUSE-based clusters.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-suse.png)
92+
![Diagram that shows the setup for an Azure Monitor for SAP solutions resource, showing the fields for SUSE-based clusters.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-suse.png)
9293
9394
1. For RHEL-based clusters, enter `http://<'IP address'>:44322/metrics?names=ha_cluster`.
9495
95-
![Diagram of the setup for an Azure Monitor for SAP solutions resource, showing the fields for RHEL-based clusters.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-rhel.png)
96+
![Diagram that shows the setup for an Azure Monitor for SAP solutions resource, showing the fields for RHEL-based clusters.](./media/provider-ha-pacemaker-cluster/azure-monitor-providers-ha-cluster-rhel.png)
9697
9798
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.
9899
@@ -110,7 +111,7 @@ Use the following troubleshooting steps for common errors.
110111
111112
### Unable to reach the Prometheus endpoint
112113
113-
When the provider settings validation operation fails with the code ‘PrometheusURLConnectionFailure’:
114+
When the provider settings validation operation fails with the code `PrometheusURLConnectionFailure`:
114115
115116
1. Restart the HA cluster exporter agent.
116117
@@ -124,7 +125,7 @@ When the provider settings validation operation fails with the code ‘Prometheu
124125
systemctl enable pmproxy
125126
```
126127
127-
1. Verify that the Prometheus endpoint is reachable from the subnet that provided while creating the Azure Monitor for SAP solutions resource.
128+
1. Verify that the Prometheus endpoint is reachable from the subnet that you provided when you created the Azure Monitor for SAP solutions resource.
128129
129130
## Next steps
130131

‎articles/sap/monitor/provider-hana.md

Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,21 +10,19 @@ ms.author: sujaj
1010
#Customer intent: As a developer, I want to create an SAP HANA provider so that I can use the resource with Azure Monitor for SAP solutions.
1111
---
1212

13+
# Configure SAP HANA provider for Azure Monitor for SAP solutions
1314

14-
# Configure SAP HANA provider for Azure Monitor for SAP solutions
15-
16-
In this how-to guide, you'll learn to configure an SAP HANA provider for Azure Monitor for SAP solutions through the Azure portal.
15+
In this how-to guide, you learn how to configure an SAP HANA provider for Azure Monitor for SAP solutions through the Azure portal.
1716

1817
## Prerequisite to enable secure communication
1918

20-
To [enable TLS 1.2 higher](enable-tls-azure-monitor-sap-solutions.md) for SAP HANA provider, follow steps mentioned in this [SAP document](https://www.sap.com/documents/2018/11/b865eb91-287d-0010-87a3-c30de2ffd8ff.html)
19+
To [enable TLS 1.2 higher](enable-tls-azure-monitor-sap-solutions.md) for the SAP HANA provider, follow the steps in [this SAP document](https://www.sap.com/documents/2018/11/b865eb91-287d-0010-87a3-c30de2ffd8ff.html).
2120

2221
## Prerequisites
2322

24-
- An Azure subscription.
23+
- An Azure subscription.
2524
- An existing Azure Monitor for SAP solutions resource. To create an Azure Monitor for SAP solutions resource, see the [quickstart for the Azure portal](quickstart-portal.md) or the [quickstart for PowerShell](quickstart-powershell.md).
2625

27-
2826
## Configure Azure Monitor for SAP solutions
2927

3028
1. Sign in to the [Azure portal](https://portal.azure.com).
@@ -34,13 +32,14 @@ To [enable TLS 1.2 higher](enable-tls-azure-monitor-sap-solutions.md) for SAP HA
3432
1. On the **Providers** tab:
3533
1. Select **Add provider**.
3634
1. On the creation pane, for **Type**, select **SAP HANA**.
37-
![Diagram of the Azure Monitor for SAP solutions resource creation page in the Azure portal, showing all required form fields.](./media/provider-hana/azure-monitor-providers-hana-setup.png)
38-
1. Optionally, select **Enable secure communication**, choose the certificate type from the drop-down menu.
39-
1. For **IP address**, enter the IP address or hostname of the server that runs the SAP HANA instance that you want to monitor. If you're using a hostname, make sure there is connectivity within the virtual network.
40-
1. For **Database tenant**, enter the HANA database that you want to connect to. It's recommended to use **SYSTEMDB**, because tenant databases don't have all monitoring views. For legacy single-container HANA 1.0 instances, leave this field blank.
35+
36+
![Diagram that shows the Azure Monitor for SAP solutions resource creation page in the Azure portal, showing all required form fields.](./media/provider-hana/azure-monitor-providers-hana-setup.png)
37+
1. Optionally, select **Enable secure communication** and choose the certificate type from the dropdown menu.
38+
1. For **IP address**, enter the IP address or hostname of the server that runs the SAP HANA instance that you want to monitor. If you're using a hostname, make sure there's connectivity within the virtual network.
39+
1. For **Database tenant**, enter the HANA database that you want to connect to. We recommend that you use **SYSTEMDB** because tenant databases don't have all monitoring views. For legacy single-container HANA 1.0 instances, leave this field blank.
4140
1. For **Instance number**, enter the instance number of the database (0-99). The SQL port is automatically determined based on the instance number.
42-
1. For **Database username**, enter the dedicated SAP HANA database user. This user needs the **MONITORING** or **BACKUP CATALOG READ** role assignment. For non-production SAP HANA instances, use **SYSTEM** instead.
43-
1. For **Database password**, enter the password for the database username. You can either enter the password directly or use a secret inside Azure Key Vault.
41+
1. For **Database username**, enter the dedicated SAP HANA database user. This user needs the **MONITORING** or **BACKUP CATALOG READ** role assignment. For nonproduction SAP HANA instances, use **SYSTEM** instead.
42+
1. For **Database password**, enter the password for the database username. You can either enter the password directly or use a secret inside Azure Key Vault.
4443
1. Save your changes to the Azure Monitor for SAP solutions resource.
4544

4645
## Next steps

‎articles/sap/monitor/provider-ibm-db2.md

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Create IBM Db2 provider for Azure Monitor for SAP solutions
3-
description: This article provides details to configure an IBM DB2 provider for Azure Monitor for SAP solutions.
3+
description: This article provides details to configure an IBM Db2 provider for Azure Monitor for SAP solutions.
44
author: MightySuz
55
ms.service: sap-on-azure
66
ms.subservice: sap-monitor
@@ -10,18 +10,18 @@ ms.author: sujaj
1010
#Customer intent: As a developer, I want to create an IBM Db2 provider so that I can monitor the resource through Azure Monitor for SAP solutions.
1111
---
1212

13-
# Create IBM Db2 provider for Azure Monitor for SAP solutions
13+
# Create IBM Db2 provider for Azure Monitor for SAP solutions
14+
15+
In this how-to guide, you learn how to create an IBM Db2 provider for Azure Monitor for SAP solutions through the Azure portal.
1416

15-
In this how-to guide, you'll learn how to create an IBM Db2 provider for Azure Monitor for SAP solutions through the Azure portal.
1617
## Prerequisites
1718

18-
- An Azure subscription.
19+
- An Azure subscription.
1920
- An existing Azure Monitor for SAP solutions resource. To create an Azure Monitor for SAP solutions resource, see the [quickstart for the Azure portal](quickstart-portal.md) or the [quickstart for PowerShell](quickstart-powershell.md).
2021

21-
## Create user for DB2 Server
22+
## Create a user for the Db2 server
2223

23-
First, create a new user for your Db2 server, for use by Azure Monitor for SAP solutions. Then, run the following script to provide the new Db2 user with appropriate permissions.
24-
Make sure to replace `<username>` with the Db2 username.
24+
First, create a new user for your Db2 server for use by Azure Monitor for SAP solutions. Then run the following script to provide the new Db2 user with appropriate permissions. Make sure to replace `<username>` with the Db2 username.
2525

2626
```sql
2727
GRANT SECADM ON DATABASE TO USER <username>;
@@ -98,27 +98,28 @@ GRANT EXECUTE ON SPECIFIC PROCEDURE SYSPROC.WLM_COLLECT_STATS_WAIT TO ROLE SAPMO
9898
GRANT EXECUTE ON SPECIFIC PROCEDURE SYSPROC.WLM_SET_CONN_ENV TO ROLE SAPMON;
9999

100100
```
101+
101102
## Prerequisites to enable secure communication
102103

103-
To [enable TLS 1.2 or higher](enable-tls-azure-monitor-sap-solutions.md), follow the steps [mentioned here](https://assets.cdn.sap.com/sapcom/docs/2018/12/d2922a3b-307d-0010-87a3-c30de2ffd8ff.pdf).
104+
To [enable TLS 1.2 or higher](enable-tls-azure-monitor-sap-solutions.md), follow the steps in [this document](https://assets.cdn.sap.com/sapcom/docs/2018/12/d2922a3b-307d-0010-87a3-c30de2ffd8ff.pdf).
104105

105-
## Create IBM Db2 provider
106+
## Create an IBM Db2 provider
106107

107108
To create the IBM Db2 provider for Azure Monitor for SAP solutions:
108109

109110
1. Sign in to the [Azure portal](https://portal.azure.com).
110-
1. Go to the Azure Monitor for SAP solutions service.
111+
1. Go to the Azure Monitor for SAP solutions service.
111112
1. Open the Azure Monitor for SAP solutions resource you want to modify.
112113
1. On the resource's menu, under **Settings**, select **Providers**.
113114
1. Select **Add** to add a new provider.
114115
1. For **Type**, select **IBM Db2**.
115-
1. *Optional* Select **Enable secure communication** and choose a certificate type from the dropdown list.
116+
1. (Optional) Select **Enable secure communication** and choose a certificate type from the dropdown list.
116117
1. Enter the IP address for the hostname.
117118
1. Enter the database name.
118119
1. Enter the database port.
119120
1. Save your changes.
120121
1. Configure more providers for each instance of the database.
121-
122+
122123
## Next steps
123124

124125
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)