Skip to content

Commit b17a31c

Browse files
authored
Merge pull request #215054 from lauradolan/sap-ams
SAP: update Azure Monitor for SAP solutions naming [bulk update]
2 parents 7668a42 + 5e78eca commit b17a31c

21 files changed

+206
-206
lines changed

articles/center-sap-solutions/faq.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ metadata:
44
description: "Get answers to common questions about Azure Center for SAP solutions (ACSS) and Virtual Instance for SAP solutions (VIS) resources."
55
ms.topic: faq
66
ms.service: azure-center-sap-solutions
7-
ms.date: 07/19/2022
7+
ms.date: 10/19/2022
88
ms.author: ladolan
99
author: lauradolan
1010

@@ -30,8 +30,8 @@ sections:
3030
answer: |
3131
No. ACSS brings Azure services together into a unified experience for deploying
3232
and managing SAP workloads on Azure. Customers can choose to use other Azure services, such as Azure
33-
Monitor for SAP solutions (AMS), independently or in an integrated manner with ACSS.
34-
AMS is an Azure-native monitoring product for customers running SAP
33+
Monitor for SAP, independently or in an integrated manner with ACSS.
34+
Azure Monitor for SAP solutions is an Azure-native monitoring product for customers running SAP
3535
landscapes on Azure. This product helps you collect data from Azure infrastructure and databases in one
3636
central location and visually correlate the data for faster troubleshooting.
3737
@@ -49,7 +49,7 @@ sections:
4949
- Software installation of SAP S4/HANA 1909 SPS 03, S/4HANA 2020 SPS 03, S/4HANA 2021 ISS 00
5050
- Registration of an existing Windows and Linux based ABAP/NetWeaver SAP system on Azure
5151
- Monitoring the health and status of an SAP system
52-
- Creating a new AMS provider or integrating an existing one
52+
- Creating a new Azure Monitor for SAP solutions provider or integrating an existing one
5353
- Starting and stopping an SAP System
5454
- Quality checks and recommendations for an SAP system with Azure Advisor
5555
- Analyze the cost of running the SAP System in Azure [non-shared resources only]

articles/center-sap-solutions/monitor-portal.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Monitor SAP system from the Azure portal (preview)
33
description: Learn how to monitor the health and status of your SAP system, along with important SAP metrics, using the Azure Center for SAP solutions (ACSS) within the Azure portal.
44
ms.service: azure-center-sap-solutions
55
ms.topic: how-to
6-
ms.date: 07/19/2022
6+
ms.date: 10/19/2022
77
author: lauradolan
88
ms.author: ladolan
99
#Customer intent: As a developer, I want to set up monitoring for my Virtual Instance for SAP solutions, so that I can monitor the health and status of my SAP system in Azure Center for SAP solutions.
@@ -17,7 +17,7 @@ In this how-to guide, you'll learn how to monitor the health and status of your
1717

1818
- Monitor your SAP system, along with its instances and VMs.
1919
- Analyze important SAP infrastructure metrics.
20-
- Create and/or register an instance of Azure Monitor for SAP solutions (AMS) to monitor SAP platform metrics.
20+
- Create and/or register an instance of Azure Monitor for SAP solutions to monitor SAP platform metrics.
2121

2222
## System health
2323

@@ -160,7 +160,7 @@ ACSS enables you to analyze important SAP infrastructure metrics from the Azure
160160

161161
## Configure Azure Monitor
162162

163-
You can also set up or register AMS to monitor SAP platform-level metrics.
163+
You can also set up or register Azure Monitor for SAP solutions to monitor SAP platform-level metrics.
164164

165165
1. Sign in to the [Azure portal](https://portal.azure.com).
166166

@@ -170,34 +170,34 @@ You can also set up or register AMS to monitor SAP platform-level metrics.
170170

171171
1. On the page for the VIS, select the VIS from the table.
172172

173-
1. In the sidebar menu for the VIS, under **Monitoring**, select **Azure Monitor for SAP**.
173+
1. In the sidebar menu for the VIS, under **Monitoring**, select **Azure Monitor for SAP solutions**.
174174

175-
1. Select whether you want to [create a new AMS instance](#create-new-ams-resource), or [register an existing AMS instance](#register-existing-ams-resource). If you don't see this option, you've already configured this setting.
175+
1. Select whether you want to [create a new Azure Monitor for SAP solutions instance](#create-new-Azure Monitor for SAP solutions-resource), or [register an existing Azure Monitor for SAP solutions instance](#register-existing-Azure Monitor for SAP solutions-resource). If you don't see this option, you've already configured this setting.
176176

177-
:::image type="content" source="media/monitor-portal/monitoring-setup.png" lightbox="media/monitor-portal/monitoring-setup.png" alt-text="Screenshot of AMS page inside a VIS resource in the Azure portal, showing the option to create or register a new instance.":::
177+
:::image type="content" source="media/monitor-portal/monitoring-setup.png" lightbox="media/monitor-portal/monitoring-setup.png" alt-text="Screenshot of Azure Monitor for SAP solutions page inside a VIS resource in the Azure portal, showing the option to create or register a new instance.":::
178178

179-
1. After you create or register your AMS instance, you are redirected to the AMS instance.
179+
1. After you create or register your Azure Monitor for SAP solutions instance, you are redirected to the Azure Monitor for SAP solutions instance.
180180

181-
### Create new AMS resource
181+
### Create new Azure Monitor for SAP solutions resource
182182

183-
To configure a new AMS resource:
183+
To configure a new Azure Monitor for SAP solutions resource:
184184

185-
1. On the **Create new AMS resource** page, select the **Basics** tab.
185+
1. On the **Create new Azure Monitor for SAP solutions resource** page, select the **Basics** tab.
186186

187-
:::image type="content" source="media/monitor-portal/ams-creation.png" lightbox="media/monitor-portal/ams-creation.png" alt-text="Screenshot of AMS creation page, showing the Basics tab and required fields.":::
187+
:::image type="content" source="media/monitor-portal/ams-creation.png" lightbox="media/monitor-portal/ams-creation.png" alt-text="Screenshot of Azure Monitor for SAP solutions creation page, showing the Basics tab and required fields.":::
188188

189189
1. Under **Project details**, configure your resource.
190190

191191
1. For **Subscription**, select your Azure subscription.
192192

193-
1. For **AMS resource group**, select the same resource group as the VIS.
193+
1. For **Azure Monitor for SAP solutions resource group**, select the same resource group as the VIS.
194194

195195
> [!IMPORTANT]
196196
> If you select a resource group that's different from the resource group of the VIS, the deployment fails.
197197
198-
1. Under **AMS instance details**, configure your AMS instance.
198+
1. Under **Azure Monitor for SAP solutions instance details**, configure your Azure Monitor for SAP solutions instance.
199199

200-
1. For **Resource name**, enter a name for your AMS resource.
200+
1. For **Resource name**, enter a name for your Azure Monitor for SAP solutions resource.
201201

202202
1. For **Workload region**, select an Azure region for your workload.
203203

@@ -211,27 +211,27 @@ To configure a new AMS resource:
211211

212212
1. Select the **Review + Create** tab.
213213

214-
### Register existing AMS resource
214+
### Register existing Azure Monitor for SAP solutions resource
215215

216-
To register an existing **AMS resource**, select the instance from the drop-down menu on the **Register AMS** page.
216+
To register an existing Azure Monitor for SAP solutions resource, select the instance from the drop-down menu on the registration page.
217217

218218
> [!NOTE]
219-
> You can only view and select the current version of AMS resources. AMS (classic) resources aren't available.
219+
> You can only view and select the current version of Azure Monitor for SAP solutions resources. Azure Monitor for SAP solutions (classic) resources aren't available.
220220
221-
:::image type="content" source="media/monitor-portal/ams-registration.png" lightbox="media/monitor-portal/ams-registration.png" alt-text="Screenshot of AMS registration page, showing the selection of an existing AMS resource.":::
221+
:::image type="content" source="media/monitor-portal/ams-registration.png" lightbox="media/monitor-portal/ams-registration.png" alt-text="Screenshot of Azure Monitor for SAP solutions registration page, showing the selection of an existing Azure Monitor for SAP solutions resource.":::
222222

223-
## Unregister AMS from VIS
223+
## Unregister Azure Monitor for SAP solutions from VIS
224224

225225
> [!NOTE]
226-
> This operation only unregisters the AMS resource from the VIS. To delete the AMS resource, you need to delete the AMS instance.
226+
> This operation only unregisters the Azure Monitor for SAP solutions resource from the VIS. To delete the Azure Monitor for SAP solutions resource, you need to delete the Azure Monitor for SAP solutions instance.
227227
228-
To remove the link between your AMS resource and your VIS:
228+
To remove the link between your Azure Monitor for SAP solutions resource and your VIS:
229229

230230
1. Sign in to the [Azure portal](https://portal.azure.com).
231231

232-
1. In the sidebar menu, under **Monitoring**, select **Azure Monitor for SAP**.
232+
1. In the sidebar menu, under **Monitoring**, select **Azure Monitor for SAP solutions**.
233233

234-
1. On the AMS page, select **Delete** to unregister the resource.
234+
1. On the Azure Monitor for SAP solutions page, select **Delete** to unregister the resource.
235235

236236
1. Wait for the confirmation message, **Azure Monitor for SAP solutions has been unregistered successfully**.
237237

articles/center-sap-solutions/view-cost-analysis.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: View post-deployment cost analysis in Azure Center for SAP solutions (pre
33
description: Learn how to view the cost of running an SAP system through the Virtual Instance for SAP solutions (VIS) resource in Azure Center for SAP solutions (ACSS).
44
ms.service: azure-center-sap-solutions
55
ms.topic: how-to
6-
ms.date: 09/23/2022
6+
ms.date: 10/19/2022
77
ms.author: kanamudu
88
author: kalyaninamuduri
99
#Customer intent: As an SAP Basis Admin, I want to understand the cost incurred for running SAP systems on Azure.

articles/virtual-machines/workloads/sap/azure-monitor-alerts-portal.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,22 +6,22 @@ ms.author: sakhare
66
ms.topic: how-to
77
ms.service: virtual-machines-sap
88
ms.subservice: baremetal-sap
9-
ms.date: 07/28/2022
9+
ms.date: 10/19/2022
1010
#Customer intent: As a developer, I want to configure alerts in Azure Monitor for SAP solutions so that I can receive alerts and notifications about my SAP systems.
1111
---
1212

1313
# Configure alerts in Azure Monitor for SAP solutions in Azure portal (preview)
1414

1515
[!INCLUDE [Azure Monitor for SAP solutions public preview notice](./includes/preview-azure-monitor.md)]
1616

17-
In this how-to guide, you'll learn how to configure alerts in Azure Monitor for SAP solutions (AMS). You can configure alerts and notifications from the [Azure portal](https://azure.microsoft.com/features/azure-portal) using its browser-based interface.
17+
In this how-to guide, you'll learn how to configure alerts in Azure Monitor for SAP solutions. You can configure alerts and notifications from the [Azure portal](https://azure.microsoft.com/features/azure-portal) using its browser-based interface.
1818

19-
This content applies to both versions of the service, AMS and AMS (classic).
19+
This content applies to both versions of the service, Azure Monitor for SAP solutions and Azure Monitor for SAP solutions (classic).
2020

2121
## Prerequisites
2222

2323
- An Azure subscription.
24-
- A deployment of an AMS resource with at least one provider. You can configure providers for:
24+
- A deployment of an Azure Monitor for SAP solutions resource with at least one provider. You can configure providers for:
2525
- The SAP application (NetWeaver)
2626
- SAP HANA
2727
- Microsoft SQL Server

articles/virtual-machines/workloads/sap/azure-monitor-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ metadata:
55
author: rdeltcheva
66
ms.service: baremetal-sap
77
ms.topic: faq
8-
ms.date: 07/21/2022
8+
ms.date: 10/19/2022
99
ms.author: radeltch
1010
title: Azure Monitor for SAP solutions FAQ (preview)
1111
summary: |

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

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: What are providers in Azure Monitor for SAP solutions? (preview)
3-
description: This article provides answers to frequently asked questions about Azure monitor for SAP solutions providers.
3+
description: This article provides answers to frequently asked questions about Azure Monitor for SAP solutions providers.
44
author: rdeltcheva
55
ms.service: virtual-machines-sap
66
ms.subservice: baremetal-sap
77
ms.topic: conceptual
8-
ms.date: 07/28/2022
8+
ms.date: 10/19/2022
99
ms.author: radeltch
1010
#Customer intent: As a developer, I want to learn what providers are available for Azure Monitor for SAP solutions so that I can connect to these providers.
1111
---
@@ -14,25 +14,25 @@ ms.author: radeltch
1414

1515
[!INCLUDE [Azure Monitor for SAP solutions public preview notice](./includes/preview-azure-monitor.md)]
1616

17-
In the context of *Azure Monitor for SAP solutions (AMS)*, a *provider* contains the connection information for a corresponding component and helps to collect data from there. There are multiple provider types. For example, an SAP HANA provider is configured for a specific component within the SAP landscape, like an SAP HANA database. You can configure an AMS resource (also known as SAP monitor resource) with multiple providers of the same type or multiple providers of multiple types.
17+
In the context of *Azure Monitor for SAP solutions*, a *provider* contains the connection information for a corresponding component and helps to collect data from there. There are multiple provider types. For example, an SAP HANA provider is configured for a specific component within the SAP landscape, like an SAP HANA database. You can configure an Azure Monitor for SAP solutions resource (also known as SAP monitor resource) with multiple providers of the same type or multiple providers of multiple types.
1818

19-
This content applies to both versions of the service, *AMS* and *AMS (classic)*.
19+
This content applies to both versions of the service, *Azure Monitor for SAP solutions* and *Azure Monitor for SAP solutions (classic)*.
2020

2121
You can choose to configure different provider types for data collection from the corresponding component in their SAP landscape. For example, you can configure one provider for the SAP HANA provider type, another provider for high availability cluster provider type, and so on.
2222

2323
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).
2424

25-
![Diagram showing AMS connection to available providers.](./media/azure-monitor-providers/providers.png)
25+
![Diagram showing Azure Monitor for SAP solutions connection to available providers.](./media/azure-monitor-providers/providers.png)
2626

27-
It's recommended to configure at least one provider when you deploy an AMS resource. By configuring a provider, you start data collection from the corresponding component for which the provider is configured.
27+
It's recommended to 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.
2828

29-
If you don't configure any providers at the time of deployment, the AMS resource is still deployed, but no data is collected. You can add providers after deployment through the SAP monitor resource within the Azure portal. You can add or delete providers from the SAP monitor resource at any time.
29+
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 within the Azure portal. You can add or delete providers from the SAP monitor resource at any time.
3030

3131
## Provider type: SAP NetWeaver
3232

33-
You can configure one or more providers of provider type SAP NetWeaver to enable data collection from SAP NetWeaver layer. AMS NetWeaver provider uses the existing [**SAPControl** Web service](https://www.sap.com/documents/2016/09/0a40e60d-8b7c-0010-82c7-eda71af511fa.html) interface to retrieve the appropriate information.
33+
You can configure one or more providers of provider type SAP NetWeaver to enable data collection from SAP NetWeaver layer. Azure Monitor for SAP solutions NetWeaver provider uses the existing [**SAPControl** Web service](https://www.sap.com/documents/2016/09/0a40e60d-8b7c-0010-82c7-eda71af511fa.html) interface to retrieve the appropriate information.
3434

35-
For the current release, the following SOAP web methods are the standard, out-of-box methods invoked by AMS.
35+
For the current release, the following SOAP web methods are the standard, out-of-box methods invoked by Azure Monitor for SAP solutions.
3636

3737
| Web method | ABAP support | Java support | Metrics |
3838
| ---------- | ------------ | ------------ | ------- |
@@ -109,7 +109,7 @@ Configuring Microsoft SQL Server provider requires:
109109

110110
## Provider type: High-availability cluster
111111

112-
You can configure one or more providers of provider type *High-availability cluster* to enable data collection from Pacemaker cluster within the SAP landscape. The High-availability cluster provider connects to Pacemaker using the [ha_cluster_exporter](https://github.com/ClusterLabs/ha_cluster_exporter) for **SUSE** based clusters and by using [Performance co-pilot](https://access.redhat.com/articles/6139852) for **RHEL** based clusters. AMS then pulls data from the database and pushes it to Log Analytics workspace in your subscription. The High-availability cluster provider collects data every 60 seconds from Pacemaker.
112+
You can configure one or more providers of provider type *High-availability cluster* to enable data collection from Pacemaker cluster within the SAP landscape. The High-availability cluster provider connects to Pacemaker using the [ha_cluster_exporter](https://github.com/ClusterLabs/ha_cluster_exporter) for **SUSE** based clusters and by using [Performance co-pilot](https://access.redhat.com/articles/6139852) for **RHEL** based clusters. Azure Monitor for SAP solutions then pulls data from the database and pushes it to Log Analytics workspace in your subscription. The High-availability cluster provider collects data every 60 seconds from Pacemaker.
113113

114114
In public preview, you can expect to see the following data with the High-availability cluster provider:
115115
- Cluster status represented as a roll-up of node and resource status
@@ -157,7 +157,7 @@ To configure an OS (Linux) provider, two primary steps are involved:
157157

158158
1. Configure an OS (Linux) provider for each BareMetal or VM node instance in your environment.
159159
To configure the OS (Linux) provider, the following information is required:
160-
- **Name**: a name for this provider, unique to the AMS instance.
160+
- **Name**: a name for this provider, unique to the Azure Monitor for SAP solutions instance.
161161
- **Node Exporter endpoint**: usually `http://<servername or ip address>:9100/metrics`.
162162

163163
Port 9100 is exposed for the **Node_Exporter** endpoint.

articles/virtual-machines/workloads/sap/azure-monitor-sap-quickstart-powershell.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: sakhare
66
ms.topic: quickstart
77
ms.service: virtual-machines-sap
88
ms.subservice: baremetal-sap
9-
ms.date: 07/21/2022
9+
ms.date: 10/19/2022
1010
ms.devlang: azurepowershell
1111
ms.custom: devx-track-azurepowershell, mode-api
1212
# Customer intent: As a developer, I want to deploy Azure Monitor for SAP solutions with PowerShell so that I can create resources with PowerShell.
@@ -16,10 +16,10 @@ ms.custom: devx-track-azurepowershell, mode-api
1616

1717
[!INCLUDE [Azure Monitor for SAP solutions public preview notice](./includes/preview-azure-monitor.md)]
1818

19-
Get started with Azure Monitor for SAP solutions (AMS) by using the
20-
[Az.HanaOnAzure](/powershell/module/az.hanaonazure/#sap-hana-on-azure) PowerShell module to create AMS resources. You'll create a resource group, set up monitoring, and create a provider instance.
19+
Get started with Azure Monitor for SAP solutions by using the
20+
[Az.HanaOnAzure](/powershell/module/az.hanaonazure/#sap-hana-on-azure) PowerShell module to create Azure Monitor for SAP solutions resources. You'll create a resource group, set up monitoring, and create a provider instance.
2121

22-
This content only applies to the AMS (classic) version of the service.
22+
This content only applies to the Azure Monitor for SAP solutions (classic) version of the service.
2323

2424
## Prerequisites
2525

0 commit comments

Comments
 (0)