Configure Azure Enhanced Monitoring Extension for SAP

By Ashwin Venugopal -

 



Overview

After deploying the VM, the Azure VM agent is automatically installed within the guest OS to further install the Azure Enhanced Monitoring Extension for SAP, which is readily available in the Azure Extension Repository. The extension can be installed by using PowerShell or CLI.

Configuring the Azure Enhanced Monitoring Extension for SAP

Azure PowerShell for Linux & Windows VMs

You can install the Azure Enhanced Monitoring Extension for SAP by using PowerShell as follows:
  • Make sure that you have installed the latest version of the Az PowerShell module.

  • For a list of available environments, run commandlet Get-AzEnvironment. If you want to use global Azure, your environment is AzureCloud but for China select AzureChinaCloud.

The script can deploy the required extensions while enabling the required features which might take several minutes. The Set-AzVMAEMExtension configuration can handle all the steps required to configure host monitoring for SAP.

The script output includes the following information:

  • Confirmation that monitoring for OS disk and all additional data disks has been configured.
  • Confirmation of the configuration of storage metrics for a specific storage account.
  • Status of the update of the monitoring configuration.
  • Confirmation that configuration has been deployed or updated.
  • List of options for testing the monitoring configuration.

You will have to wait for at least 15-30 minutes for Azure Diagnostics to collect the relevant data.

Azure CLI for Linux VMs

For installing the Azure Enhanced Monitoring Extension for SAP by using Azure CLI:
  1. Install using CLI 2.0
  2. Sign in with your Azure account: az login
  3. install Azure CLI AEM Extension: az extension add --name aem
  4. Install the extension: az vm aem set  -g  <resource-group-name>  -n  <vm name> 

Checks & troubleshooting for end-to-end monitoring

After successfully deploying your Azure VM and setting up the relevant Azure monitoring infrastructure, you have to check whether all the components of Azure Enhance Monitoring Extension are working as expected or not. 

Firstly, run the readiness check, if all the results are positive as well as all relevant performance counters appear fine then, you can say that Azure monitoring has been set up successfully and you can further proceed with the installation of SAP Host Agent. However, if the readiness check indicates that the counters are missing, you will have to run the health check for the Azure monitoring infrastructure. 











Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more