Note: In Linux OS systems, Azure deploys the Linux Diagnostics Extension (LAD) v2.3 automatically to gather these metrics.  Refer to Microsoft Azure documentation for supported Linux OS versions and troubleshooting enabling LAD.

* LAD v2.3 when using Azure distributions Endorsed distributions of Linux | Microsoft Docs 

* LAD v3.0 azure-linux-extensions/Diagnostic at master · Azure/azure-linux-extensions · GitHub 

* There is a known issue with CoreOS support, follow the issue here: [LAD] CoreOS support · Issue #66 · Azure/azure-linux-extensions · GitHub  

* Have a supported Linux OS and still having trouble? Check out this article: https://github.com/Azure/azure-linux-extensions/issues/488  

Steps for New VMs

Step 1: Login to your Azure Portal (https://portal.azure.com)

Step 2: If you are creating a new VM, then make sure you have "Guest OS diagnostic" Enabled  - once enabled you must provide a storage account detail

If you have previously deployed VMs please follow the steps mentioned below:

Steps For Existing Windows VMs:

• Click a Windows VM
• Select Diagnostics settings from the Azure UI blade
• Under the Overview tab:
  • Pick a Storage account: Select your storage account so that the metrics stats can be stored
  • Click 'Enable guest level monitoring' and wait for the process to complete

Confirmation Message

• Click the 'Performance  Counters' tab of the VM and ensure Memory is checked.  If you do not need any other Performance Counters or Logs enabled you can only leave Memory enabled and remove all other logging from the Logs tab.  As Turbonomic only needs the Memory Performance Counter as well it will help to save space on the storage account. 
  

• After you enable Basic metrics the Save button should be enabled so you can save the settings. The screenshot below shows an example of how it will look after enabling basic metrics.
  

Steps For Existing Linux VMs:

• Click a Linux VM
• Select Diagnostics settings from the Azure UI Blade  
• Under the Overview tab:
  • Pick a Storage account: Select your storage account so that the metrics stats can be stored
  • Click 'Enable guest level monitoring' and wait for the process to complete

Confirmation Message

• Click the 'Metrics' tab and make sure the Memory option is checked.  If you do not need any other Metrics or Syslog enabled you can only leave Memory enabled and remove all other logging from the Syslog tab.  As Turbonomic only needs the Memory Metric as well it will help to save space on the storage account.  

• After you enable Basic metrics the Save button should be enabled so you can save the settings. The screenshot below shows an example of how it will look after enabling basic metrics.

Step 6: Double check the DateTime value in the Turbonomic VM  

• There have been a few situations where an out-of-sync clock on the Turbonomic VM can prevent vMemory utilization values from being populated as a result of not being able to communicate with the Azure Storage Account. To clarify, when we say "out-of-sync clock" we just mean that the actual time that the Turbonomic VM knows should match up (+/- 2 min) with the timezone it is configured to.

• To confirm that the clock is in sync, open a PuTTY session to the Turbonomic VM and type in the "date" command. This will return the date, time and timezone that the VM knows:

• Again, make sure that the time value (in this case it is 9:20 AM) matches up with the timezone recognized (in this case EDT). The above example is from a properly synchronized clock, however, if the time value returned was 9:00 AM, then this clock would be out sync with the EDT timezone it is set to and needs to be reconfigured.

•  To resolve/avoid these issues, just sync up the Turbonomic VM with an NTP server