In this document, we will be looking at how we can enable Basic Metrics on Azure. This document will cover how to do this manually. If you don't have Basic Metrics enabled then Azure will not be collecting Memory Stats and Turbonomic will not be able to pull this information from Azure.
Note: In Linux OS systems, Azure will deploy 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
* 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
Step 1: Login to your Azure Portal (http://azure.portal.com)
Step 2: If you are creating a new VM then make sure you have "Guest OS diagnostic" Enabled.
If you have previous VMs then follow the steps mentioned below.
Step 3: Select the VM you would like Turbonomic to Monitor Memory Metrics for.
Step 4: Select "Diagnostic Settings"
- For Windows VMs
- For Linux VMs
- Select Diagnostics settings
- Make sure the Status is On
- Storage account: - Select your storage account so that the metrics stats can be stored
- Make sure the Basic metrics option is checked
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.
After you enable Basic Metrics you will be able to see a lot more Metrics on the Metrics sections.
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 or use the OpenSuse yast command to manually adjust the clock.