|
1 | 1 | --- |
2 | | -title: SAP Monitoring with Azure Monitor for SAP |
3 | | -description: Configure Azure Monitor for SAP with SAP Deployment Automation Framework. |
| 2 | +title: Configure Azure Monitor for SAP with SAP Deployment Automation Framework |
| 3 | +description: Learn how to configure Azure Monitor for SAP with SAP Deployment Automation Framework to automate monitoring of your SAP landscape. |
4 | 4 | author: devanshjain |
5 | 5 | ms.author: devanshjain |
6 | 6 | ms.reviewer: kimforss |
7 | | -ms.date: 02/25/2024 |
| 7 | +ms.date: 04/01/2026 |
8 | 8 | ms.topic: how-to |
9 | 9 | ms.service: sap-on-azure |
10 | 10 | ms.subservice: sap-automation |
11 | | -ms.custom: |
12 | 11 | # Customer intent: As an SAP administrator, I want to automate the deployment and monitoring of SAP systems using Azure Monitor and the SAP Deployment Automation Framework, so that I can ensure optimal performance and availability while reducing complexity and costs. |
13 | 12 | --- |
14 | | -# Configure Azure monitor for SAP with SAP Deployment Automation Framework |
15 | 13 |
|
16 | | -Monitoring the performance and availability of SAP systems on Azure is simplified through [Azure Monitor for SAP](../monitor/about-azure-monitor-sap-solutions.md). It collects and analyzes metrics and logs from your applications, databases, operating systems, and Azure resources. Customers use Azure Monitor for SAP to visualize and troubleshoot issues, set alerts and notifications, and optimize SAP workloads on Azure. |
| 14 | +# Configure Azure Monitor for SAP with SAP Deployment Automation Framework |
17 | 15 |
|
18 | | -By integrating Azure Monitor for SAP and SAP Deployment Automation Framework, you can achieve a faster, easier, and more reliable deployment and operation of your SAP systems on Azure. You can use the automation framework to provision and configure the SAP systems, and Azure Monitor for SAP to monitor and optimize the performance and availability of those SAP systems. |
| 16 | +Azure Monitor for SAP is an Azure-native monitoring product for SAP landscapes running on Azure. SAP Deployment Automation Framework is an open-source orchestration tool that deploys, installs, and maintains SAP environments on Azure. Setting up monitoring manually across the databases, operating systems, and clusters in an SAP landscape is complex and error-prone. |
19 | 17 |
|
20 | | -This integration with [SAP on Azure Deployment Automation Framework](deployment-framework.md) enables you to reduce the complexity and deployment cost of running your SAP environments on Azure, by helping to automate the monitoring of different components of an SAP landscape. |
| 18 | +In this article, you configure Azure Monitor for SAP as part of your SAP Deployment Automation Framework deployment so that the framework automatically provisions monitoring alongside your SAP infrastructure. For more information, see [Azure Monitor for SAP](../monitor/about-azure-monitor-sap-solutions.md) and [SAP Deployment Automation Framework](deployment-framework.md). |
21 | 19 |
|
22 | | -## Overview |
| 20 | +> [!NOTE] |
| 21 | +> The automation framework currently supports deploying Azure Monitor for SAP resources, the [OS (Linux) provider](../monitor/about-azure-monitor-sap-solutions.md#os-linux-data) for monitoring Azure virtual machines (VMs), and the [HA Pacemaker cluster provider](../monitor/about-azure-monitor-sap-solutions.md#ha-pacemaker-cluster-data) for monitoring high-availability clusters. |
23 | 22 |
|
24 | | -As described in the [overview document](deployment-framework.md), the automation framework has two main components: |
| 23 | +## Understand the architecture |
25 | 24 |
|
26 | | -- Deployment infrastructure (control plane, typically deployed in the hub) |
27 | | -- SAP infrastructure (SAP workload zone, typically deployed in a spoke) |
| 25 | +The automation framework deploys one Azure Monitor for SAP resource per [workload zone](deployment-framework.md#about-the-sap-workload-zone). The resource monitors performance and availability for all SAP systems in that environment. |
28 | 26 |
|
29 | | -Deployment of Azure Monitor for SAP (AMS) and the [providers](../monitor/about-azure-monitor-sap-solutions.md#what-can-you-monitor) can be automated from the SAP Deployment Automation Framework (SDAF) to simplify the monitoring process. In this architecture, one Azure Monitor for SAP resource is deployed in each [workload zone](deployment-framework.md#about-the-sap-workload-zone), which represents the environment. This resource is responsible for monitoring the performance and availability of different components of the SAP systems in that environment. |
| 27 | +:::image type="content" source="./media/deployment-framework/control-plane-sap-infrastructure-monitor.png" alt-text="Diagram that shows the dependency between the control plane, and application plane for SAP Deployment Automation Framework with Azure Monitor for SAP." lightbox="./media/deployment-framework/control-plane-sap-infrastructure-monitor.png"::: |
30 | 28 |
|
31 | | -:::image type="content" source="./media/deployment-framework/control-plane-sap-infrastructure-monitor.png" alt-text="Diagram that shows the dependency between the control plane, the application plane for SAP Deployment Automation Framework with Azure monitor for SAP." lightbox="./media/deployment-framework/control-plane-sap-infrastructure-monitor.png"::: |
| 29 | +The automation framework performs the following steps: |
32 | 30 |
|
33 | | -To monitor different components of each SAP system, there are corresponding providers and all these providers are deployed in the Azure Monitor for SAP resource of that environment. This setup allows for efficient monitoring and management of the SAP systems, as all the providers for a particular system are located in the same Azure Monitor for SAP resource. The automation framework automates the following steps: |
34 | | -- Creates Azure Monitor for SAP resource in workload zone. |
35 | | -- Performs prerequisites steps required to enable monitoring. |
36 | | -- Creates providers for each component of SAP landscape in Azure Monitor for SAP resource created. |
| 31 | +- Creates the Azure Monitor for SAP resource in the workload zone. |
| 32 | +- Performs prerequisite steps required to enable monitoring. |
| 33 | +- Creates [providers](../monitor/about-azure-monitor-sap-solutions.md#what-can-you-monitor) for each monitored component of the SAP landscape. |
37 | 34 |
|
38 | | -> [!NOTE] |
39 | | -> This automation framework currently supports deployment automation of Azure monitor for SAP resource, [OS (Linux) provider](../monitor/about-azure-monitor-sap-solutions.md#os-linux-data) to monitor the Azure VMs, and [HA Pacemaker cluster provider](../monitor/about-azure-monitor-sap-solutions.md#ha-pacemaker-cluster-data) to monitor the high availability clusters in the SAP system. |
| 35 | +The Azure Monitor for SAP resource deployed in the workload zone resource group includes the following [key components](../monitor/about-azure-monitor-sap-solutions.md#what-is-the-architecture): |
| 36 | + |
| 37 | +- Azure Monitor for SAP resource |
| 38 | +- Managed resource group that includes: |
| 39 | + - Azure Functions resource |
| 40 | + - Azure Key Vault |
| 41 | + - Log Analytics workspace (optional) |
| 42 | + - Storage account |
| 43 | + |
| 44 | +## Prerequisites |
| 45 | + |
| 46 | +- An Azure subscription. If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn). |
| 47 | +- A deployed SAP Deployment Automation Framework [control plane](deployment-framework.md). |
| 48 | +- A deployed [SAP workload zone](deployment-framework.md#about-the-sap-workload-zone). |
| 49 | +- Terraform installed on your deployment system. |
| 50 | + |
| 51 | +## Configure the workload zone for Azure Monitor for SAP |
| 52 | + |
| 53 | +Add the Azure Monitor for SAP parameters to your workload zone Terraform variables file (`.tfvars`). Optionally, you can use an existing Log Analytics workspace in the same subscription as your workload zone. |
| 54 | + |
| 55 | +1. Open your workload zone `.tfvars` file in an editor. |
| 56 | + |
| 57 | +1. Add the subnet configuration for Azure Monitor for SAP. Set `ams_subnet_address_prefix` to a valid subnet address range in your virtual network. |
| 58 | + |
| 59 | + ```terraform |
| 60 | + ######################################################################################### |
| 61 | + # AMS subnet variables # |
| 62 | + ######################################################################################### |
| 63 | +
|
| 64 | + # ams_subnet_name is an optional parameter and should only be used if the default naming is not acceptable |
| 65 | + # ams_subnet_name = "" |
| 66 | +
|
| 67 | + # ams_subnet_address_prefix is a mandatory parameter if the subnets are not defined in the workload or if existing subnets are not used |
| 68 | + ams_subnet_address_prefix = "10.242.25.0/24" |
| 69 | +
|
| 70 | + # ams_subnet_arm_id is an optional parameter that if provided specifies Azure resource identifier for the existing subnet to use |
| 71 | + # ams_subnet_arm_id = "" |
40 | 72 |
|
41 | | -The [key components](../monitor/about-azure-monitor-sap-solutions.md#what-is-the-architecture) of the Azure monitor for SAP resource created in the workload zone resource group would include: |
42 | | -- Azure monitor for SAP resource |
43 | | -- Managed Resource group with in the Azure monitor for SAP that includes: |
44 | | - - Azure functions resource |
45 | | - - Azure Key Vault |
46 | | - - Log analytics workspace (optional) |
47 | | - - Storage account |
| 73 | + # ams_subnet_nsg_name is an optional parameter and should only be used if the default naming is not acceptable for the network security group name |
| 74 | + # ams_subnet_nsg_name = "" |
48 | 75 |
|
49 | | -## Workload zone configuration for Azure Monitor for SAP resource |
| 76 | + # ams_subnet_nsg_arm_id is an optional parameter that if provided specifies Azure resource identifier for the existing network security group to use |
| 77 | + # ams_subnet_nsg_arm_id = "" |
| 78 | + ``` |
50 | 79 |
|
51 | | -The example shows the parameters that are required for the deployment of Azure Monitor for SAP resource in the workload zone. Optionally, you can choose to use an existing log analytics workspace that exists in the same subscription as your workload zone. |
| 80 | +1. Add the Azure Monitor for SAP instance configuration. Set `create_ams_instance` to `true` and configure the instance name. |
52 | 81 |
|
53 | | -```terraform |
54 | | -######################################################################################### |
55 | | -# AMS Subnet variables # |
56 | | -######################################################################################### |
| 82 | + ```terraform |
| 83 | + ######################################################################################### |
| 84 | + # AMS instance variables # |
| 85 | + ######################################################################################### |
57 | 86 |
|
58 | | -# If defined these parameters control the subnet name and the subnet prefix |
59 | | -# ams_subnet_name is an optional parameter and should only be used if the default naming is not acceptable |
60 | | -# ams_subnet_name = "" |
| 87 | + # create_ams_instance is an optional parameter, and should be set true if the AMS instance is to be created. |
| 88 | + create_ams_instance = true |
61 | 89 |
|
62 | | -# ams_subnet_address_prefix is a mandatory parameter if the subnets are not defined in the workload or if existing subnets are not used |
63 | | -ams_subnet_address_prefix = "10.242.25.0/24" |
| 90 | + # ams_instance_name is an optional parameter and should only be used if the default naming is not acceptable |
| 91 | + ams_instance_name = "AMS-RESOURCE" |
64 | 92 |
|
65 | | -# ams_subnet_arm_id is an optional parameter that if provided specifies Azure resource identifier for the existing subnet to use |
66 | | -#ams_subnet_arm_id = "" |
| 93 | + # ams_laws_arm_id is an optional parameter to use an existing Log Analytics workspace for the AMS instance |
| 94 | + ams_laws_arm_id = "/subscriptions/<subscription-id>/resourcegroups/<rg-name>/providers/microsoft.operationalinsights/workspaces/<workspace-name>" |
| 95 | + ``` |
67 | 96 |
|
68 | | -# ams_subnet_nsg_name is an optional parameter and should only be used if the default naming is not acceptable for the network security group name |
69 | | -# ams_subnet_nsg_name = "" |
| 97 | +1. Save and close the file. |
70 | 98 |
|
71 | | -# ams_subnet_nsg_arm_id is an optional parameter that if provided specifies Azure resource identifier for the existing network security group to use |
72 | | -# ams_subnet_nsg_arm_id = "" |
| 99 | +1. Deploy the workload zone with the updated configuration by running the deployment script for your workload zone. |
73 | 100 |
|
74 | | -######################################################################################### |
75 | | -# AMS instance variables # |
76 | | -######################################################################################### |
| 101 | +## Configure system providers for Azure Monitor for SAP |
77 | 102 |
|
78 | | -# If defined these parameters control the ams instance (Azure monitor for SAP) |
79 | | -# create_ams_instance is an optional parameter, and should be set true is the AMS instance is to be created. |
80 | | -create_ams_instance = true |
| 103 | +To enable OS and high-availability cluster monitoring, add the monitoring provider parameters to your SAP system Terraform variables file (`.tfvars`). |
81 | 104 |
|
82 | | -# ams_instance_name is an optional parameter and should only be used if the default naming is not acceptable |
83 | | -ams_instance_name = "AMS-RESOURCE" |
| 105 | +1. Open your SAP system `.tfvars` file in an editor. |
84 | 106 |
|
85 | | -# ams_laws_arm_id is a optional parameter to use an existing log analytics for the AMS instance |
86 | | -ams_laws_arm_id = "/subscriptions/0000000-000000-0000000-0000000000/resourcegroups/rg-name/providers/microsoft.operationalinsights/workspaces/workspacename" |
| 107 | +1. Add the following parameters. Set each parameter to `true` for the provider types you want to enable. |
87 | 108 |
|
88 | | -``` |
| 109 | + ```terraform |
| 110 | + # enable_os_monitoring is an optional parameter and should be set to true if you want to monitor the Azure VMs of your SAP system. |
| 111 | + enable_os_monitoring = true |
89 | 112 |
|
90 | | -## System configuration for AMS providers |
| 113 | + # enable_ha_monitoring is an optional parameter and should be set to true if you want to monitor the HA clusters of your SAP system. |
| 114 | + enable_ha_monitoring = true |
| 115 | + ``` |
91 | 116 |
|
92 | | -The following example shows the parameter that is required for the automation of provider prerequisites and provider creation in the Azure monitor for SAP. |
| 117 | +1. Save and close the file. |
93 | 118 |
|
94 | | -```terraform |
95 | | -# enable_os_monitoring is an optional parameter and should be set to true if you want to monitor the Azure VMs of your SAP system. |
96 | | -enable_os_monitoring = true |
| 119 | +1. Deploy the SAP system with the updated configuration by running the system deployment script. |
97 | 120 |
|
98 | | -# enable_ha_monitoring is an optional parameter and should be set to true if you want to monitor the HA clusters of your SAP system. |
99 | | -enable_ha_monitoring = true |
| 121 | +## Related content |
100 | 122 |
|
101 | | -``` |
| 123 | +- [What is Azure Monitor for SAP?](../monitor/about-azure-monitor-sap-solutions.md) |
| 124 | +- [SAP Deployment Automation Framework](deployment-framework.md) |
| 125 | +- [Providers for Azure Monitor for SAP](../monitor/about-azure-monitor-sap-solutions.md#what-can-you-monitor) |
0 commit comments