Azure Virtual Machine (classic) Test

Azure Virtual Machines is one of several types of on-demand, scalable computing resources that Azure offers. An Azure virtual machine gives you the flexibility of virtualization without having to buy and maintain the physical hardware that runs the virtual machine. Azure Virtual Machines lets you create and use virtual machines in the cloud.

Azure Virtual Machines lets you create and use virtual machines in the cloud. Providing what's known as Infrastructure as a Service (IaaS), virtual machine technology can be used in variety of ways. Some examples are:

Virtual machines (VMs) for development and test. Development groups commonly use VMs because they offer a quick, easy way to create a computer with specific configurations required to code and test an application. Azure Virtual Machines provides a straightforward and economical way to create these VMs, use them, then delete them when they're no longer needed.

Running applications in the cloud. It makes economic sense to run some applications in the public cloud. One example is an application that has large spikes in demand. Although you could equip your own data center with enough hardware to handle peak demand, that hardware might be underutilized much of the time. Running this application on Azure lets you pay for extra VMs only when you need them and shut them down when you don't. Or, suppose you're a start-up that needs on-demand computing resources quickly and with no commitment. Once again, Azure can be the right choice.

Extending your own datacenter into the public cloud. When you use Azure Virtual Network, your organization can create a virtual network (VNET) that's an extension of your own on-premises network and add VMs to that VNET. This allows running applications such as SharePoint, SQL Server and others on an Azure VM. This approach might be easier to deploy or less expensive than running them in VMs your own datacenter.

Disaster recovery. Rather than paying continuously for a backup datacenter that's rarely used, IaaS-based disaster recovery lets you pay for the computing resources you need only when you really need them. For example, if your primary datacenter goes down, you can create VMs running on Azure to run essential applications, then shut them down when they're no longer needed.

When multiple virtual machines are hosted on the Azure cloud, administrators may often want to figure out if each virtual machine in the cloud is used optimally. In order to closely monitor the virtual machine and figure out the resource utilization of each virtual machine, administrators can use the Azure Virtual Machine (classic) test.

This test monitors the current state and the amount of resources that each virtual machine on the Azure cloud is taking up. Using the metrics reported by this test, administrators can determine which virtual machine in the cloud is taking up most CPU, which virtual machine is generating the most network traffic, which virtual machine has the maximum IOPS, etc.

Note:

eG Enterprise cannot auto-discover and monitor the Virtual Machines deployed through the Azure Resource Manager whereas Virtual Machines deployed in Azure Classic mode can be monitored.

This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick Microsoft Azure as the Component type, Performance as the Test type, choose this test from the disabled tests list, and click on the < button to move the test to the ENABLED TESTS list. Finally, click the Update button.

Target of the Test: Microsoft Azure

Agent deploying the test: A remote agent

Output of the test: One set of results for each virtual machine of the target Microsoft Azure being monitored

First level Descriptor: Virtual Machine

  1. TEST PERIOD - How often should the test be executed
  2. Host– The host for which the test is being configured
  3. SUBSCRIPTION ID- Specify the GUID which uniquely identifies your subscription to the target Microsoft Azure that is to be monitored.
  4. CERTIFICATE PATH - In order to collect metrics from the target Microsoft Azure, the eG agent communicates via Microsoft Azure Service Management API Requests. By default, a management certificate is required to authenticate Microsoft Azure Service Management API Requests. The Management certificate should be associated with the subscription ID. The management certificate can be created on your own or you can request Microsoft Azure portal to create a certificate on behalf of you. Prior to creating a management certificate, you have to create a keystore. The steps for creating a management certificate and the keystore is discussed elaborately in Section 1.1. The created keystore will reside in the <JAVA_INSTALL_DIR>\jre7\bin folder. Specify the exact path to the keystore file in this text box. If you have requested Microsoft Azure portal to create the management certificate, then, specify the exact path on which you have stored the keystore file. For example, if the keystore file created is WindowsAzureKeyStore.jks and if you have stored it in D:\Azure folder, then specify the CERTIFICATE PATH as D:\Azure\WindowsAzureKeyStore.jks.
  5. CERTIFICATE PASSWORD - Specify the password that is provided while creating the keystore in this text box.
  6. confirm password - Confirm the password by retyping it here.
  7. dd frequency - Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
  8. detailed diagnosis - To make diagnosis more efficient and accurate, the eG system embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability.
    • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

Measures reported by the test:

Measurement Description Measurement Unit Interpretation

Status

Indicates the current status of this virtual machine.

 

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
RoleStateUnknown 1
CreatingVM 2
StartingVM 3
CreatingRole 4
StartingRole 5
Running 6
BusyRole 7
StoppingRole 8
StoppedRole 9
StoppingVM 10
StoppedVM 11
RestartingRole 12
CyclingRole 13
FailedStartingRole 14
FailedStartingVM 15
UnresponsiveRole 16
StoppedDeallocated 17
Offline 0

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current status of this virtual machine. The graph of this measure however, represents the status of a server using the numeric equivalents only - 0 to 17.

The detailed diagnosis of this measure if enabled, lists the operating system that is running on the virtual machine, the size of the role instance, the location of the virtual machine, the virtual disk name, the host cache and the media link.

Disk reads

Indicates the rate at which data is read from the disks of this virtual machine.

MB/sec

A high value of this measure indicates that the disks are experiencing high I/O activity.

Disk writes

Indicates the rate at which data is written from the disks of this virtual machine.

MB/sec

 

Incoming network traffic

Indicates the amount of data bytes received by all the network interfaces connected to this virtual machine.

MB

Comparing the value of this measure across the virtual machines will help you to identify the virtual machine that is hogged with incoming network data.

Outgoing network traffic

Indicates the amount of data bytes sent through all the network interfaces connected to this virtual machine.

MB

Comparing the value of this measure across the virtual machines will help you to identify the virtual machine through which maximum amount of data traffic passes through.

CPU utilization

Indicates the average percentage of CPU utilized by this virtual machine.

Percent

A very high value of this measure indicates that the VM is currently utilizing high memory resources.

Total core

Indicates the total number of CPU cores allocated to this virtual machine.

Number

 

Configured memory

Indicates the amount of memory that is configured for this virtual machine.

GB

 

Maximum disk size:

Indicates the maximum amount of disk space allocated for this virtual machine.

GB

 

Temporary disk size

Indicates the amount of temporary disk space that is allocated for this virtual machine.

GB

 

Maximum data disk

Indicates the maximum number of data disks allocated to this virtual machine.

Number

 

Maximum IOPS

Indicates the maximum amount of data space allocated for IOPS on this virtual machine.

GB