One SAP support prerequisite for running SAP on Azure, is that you must have Azure Enhanced Monitoring for Linux installed onto the Azure Linux VMs where your SAP application runs (including DB servers). Details are in SAP note 2015553.
In this brief post I show how to check if it is already installed, then how to install it, without needing to install the Powershell Azure Cmdlets.
What is Azure Enhanced Monitoring for Linux?
Azure Enhanced Monitoring for Linux (AEM) is an Azure VM extension installed onto the target Linux VM.Azure Instance Agent to pull additional telemetry information down onto the local VM, and places it into a file on the Linux file system called /var/lib/AzureEnhancedMonitor/PerfCounters .
This special file is pure ASCII text with data inside that is semi-colon separated.
The file is parsed by the SAP Host Agent (also installed on every SAP VM) and made available in the monitoring memory segment used by the Netweaver ABAP stack, with the data being visible in transaction ST06 (OS06).
How to Check if AEM Is Installed
There are a number of ways to check if Azure Enhanced Monitoring for Linux is installed on a VM:
Inside the VM in Linux we can check for the existence of file: “/var/lib/AzureEnhancedMonitor/PerfCounters” Inside the VM in Linux we can check the extension home dir exists: “/var/lib/waagent/Microsoft.OSTCExtensions.AzureEnhancedMonitorForLinux-*” In the Azure Portal, we can check the status of the extension in the Azure Portal: In the Azure Cloud Shell, we can either Test or Get the AEM Extension to see if it is installed: Get-AzVMAEMExtension -ResourceGroupName <RG-NAME> -VMName <VM-Name>
Test-AzVMAEMExtension -ResourceGroupName <RG-NAME> -VMName <VM-Name>
Installing AEM
There are two ways to install the Azure Enhanced Monitoring for Linux extension into a VM:
Using local PowerShell (on your computer) with the Azure Cmdlets installed. Using Powershell in the Azure Portal Cloud Shell. Out of the two options, I usually opt for the Cloud Shell. Once you have it setup, you will find you can use it for many other things and access it from anywhere!
To install the AEM extension, we use Powershell commands to do the following sequence of tasks:
Obtain our subscription context. Deploy the extension to the specific VM in the subscription. Let’s start the Cloud Shell (NOTE: You will need a Storage Account for the Cloud Shell to work).
Make sure that you are in a PowerShell Shell:
We may need to switch to a specific subscription.
Get-AzSubscription | Select-Object Id We can then set the context of our Cloud Shell to the specific subscription Id as follows:
$context = Get-AzSubscription -SubscriptionId '<SubscriptionID>'
Set-AzContext -SubscriptionObject $context Once the code has executed, we can check if the AEM extension is already installed:
Get-AzVMAEMExtension -ResourceGroupName <RG-NAME> -VMName <VM-Name> If the AEM extension is already installed, then we will see output being returned from the Get command:
ResourceGroupName : UK-West
VMName : vm01
Name : AzureEnhancedMonitorForLinux
Location : ukwest
Etag : null
Publisher : Microsoft.OSTCExtensions
ExtensionType : AzureEnhancedMonitorForLinux
TypeHandlerVersion : 3.0
Id : /subscriptions/mybigid/resourceGroups/UK-West/providers/Microsoft.Compute/virtualMachines
/vm01/extensions/AzureEnhancedMonitorForLinux
PublicSettings : {
"cfg": [
{
"key": "vmsize",
"value": "Standard_D4s_v3"
},
{
"key": "vm.role",
"value": "IaaS"
},
{
"key": "vm.memory.isovercommitted",
"value": 0
},
{
"key": "vm.cpu.isovercommitted",
"value": 0
},
{
"key": "script.version",
"value": "3.0.0.0"
},
{
"key": "verbose",
"value": "0"
},
{
"key": "href",
"value": "http://aka.ms/sapaem"
},
{
"key": "vm.sla.throughput",
"value": 96
},
{
"key": "vm.sla.iops",
"value": 6400
},
{
"key": "wad.isenabled",
"value": 0
}
]
}
ProtectedSettings :
ProvisioningState : Succeeded
Statuses :
SubStatuses :
AutoUpgradeMinorVersion : True
ForceUpdateTag : 637516905202791108
EnableAutomaticUpgrade :
Set-AzVMAEMExtension -ResourceGroupName <RG-NAME> -VMName <VM-Name> The extension should be installed successfully.
There is a “Test” command that you can call to test the AEM:
Test-AzVMAEMExtension -ResourceGroupName <RG-NAME> -VMName <VM-Name> Finally, if you want to see the additional command line options, then use the standard “Get-Help” as follows:
Get-Help Set-AzVMAEMExtension -Full
Issues with AEM
There’s one known issue with Azure Enhanced Monitoring for Linux, the number of data disks reported in the PerfCounters file seems to be limited to 9.
You may also be interested in:
