1. Prerequisites
  2. Download Azure CLI commands
  3. Download AppNeta files
  4. Login to Azure
  5. Create a resource group and storage account
  6. Run the export commands
  7. Create the VM image
  8. Download APM connection information
  9. Create the v35 configuration file
  10. Create the v35
  11. Verify that you can access the v35
  12. Configure for web proxy if required
  13. Assign licenses
  14. Set the monitoring point location
  15. Set up monitoring

The AppNeta v35 is a virtual monitoring point that runs as a virtual machine on a host system. This version of the v35 runs on Microsoft Azure. The virtual machine is sized as “Standard_F4s_v2” and uses accelerated networking. At this time, the v35 for Azure is only available as a target monitoring point for Delivery monitoring. It cannot be used as a source monitoring point and does not support Experience or Usage monitoring.

v35 for Azure is only supported on APM-Private Cloud. It is not supported on APM-Public Cloud.

Prerequisites

You need to have the following in place prior to creating a v35 on Azure:

  • A Linux machine. The installation is run from this machine.
    • It must have an SSH public key (~/.ssh/id_rsa.pub) available.
    • It requires the following packages to be loaded:
      • jq
      • qemu-utils
      • base64
      • sh
  • A Microsoft Azure account.

Download Azure CLI commands

The scripts used in this procedure make use of Azure CLI commands. These commands must be downloaded onto your installation machine so that the scripts can use them. Follow the instructions for installing the commands at Install Azure CLI 2.0 on the Microsoft documentation portal.

Download AppNeta files

The procedure requires a number of AppNeta-created files (installation scripts (.sh), a VM configuration file (.json), and an image file (.vhd)). These must also be downloaded to your installation machine.

The scripts and configuration file can be found here. You will need to unzip them.
The image file can be found here.

Login to Azure

In order to run Azure commands, you first need to log in to the Microsoft Azure Cross-platform Command Line Interface application.

az login

Follow the directions that appear. The output looks as follows:

[
  {
    "cloudName": "AzureCloud",
    "id": "<id>",
    "isDefault": true,
    "name": "<subscription name>",
    "state": "Enabled",
    "tenantId": "<tenant id>",
    "user": {
      "name": "<your user name>",
      "type": "user"
    }
  }
]

Create a resource group and storage account

A resource group is a logical container used for deploying and managing Azure resources. A storage account is required within the resource group to house data objects. A resource group and a storage account must be created prior to creating a virtual machine. Create a resource group and storage account as follows:

./az-group-create.sh -g <resource group name> -a <storage account> [-l <azure location>]

Command line options include:

  • -g <resource group name> - the name to use for your resource group
  • -a <storage account> - the name to use for your storage account associated with the resource group

Optional command line options include:

  • -l <azure location> - the Azure location the VM will run in (default: eastus)

Note: See naming rules and restrictions for Azure resources for restrictions on naming the resource group and storage account.

Make note of the following from the output:

  • AZ Resource Group
  • AZ Storage Account
  • AZ Storage Container
  • AZ Storage Key

Run the export commands

To simplify the steps that follow, export the variables returned by the previous step by running the following commands:

export AZURE_STORAGE_ACCOUNT_CONTAINER=<AZ Storage Container>
export AZURE_STORAGE_ACCOUNT=<AZ Storage Account>
export AZURE_STORAGE_KEY="<AZ Storage Key>"
export AZURE_RESOURCE_GROUP=<AZ Resource Group>

You can confirm that the variables are exported properly using:

echo $<variable name>

For example:

echo $AZURE_STORAGE_ACCOUNT_CONTAINER

Create the VM image

Once the resource group and storage account are created, use the AppNeta image file to create the VM image:

./az-image-create.sh -i <image file>

Alternatively, if the export commands were not run in the previous step:

./az-image-create.sh -g <resource group name> -a <storage account> -k <storage key> -c <storage container> -i <image file>

Command line options include:

  • -g <resource group name> - the name of your resource group
  • -a <storage account> - the name of the storage account associated with the resource group
  • -k <storage key> - the key associated with the storage account
  • -c <storage container> - the name of your storage container within the storage account
  • -i <image file> - the name of the AppNeta image file (for example, pathview-amd64.vhd)

Download APM connection information

The v35 requires information on how to connect to APM. This is acquired from APM. To download the APM connection information:

  1. Log in to APM.
  2. Change organization to the one you will use the v35 with.
  3. Navigate to > Manage Monitoring Points > + Add Monitoring Points > Physical Monitoring Point > Direct Connect.
  4. Click Download File.
    • The nis.config file is downloaded to your computer. It looks as follows:
	NIS Address: <nis address>
	NIS Ports: 8080,80
	NIS Protocol: TCP
	SSL: true
	Site Key: <site key>
	Job Timeout: 7200
	Welcome URL: https://<nis address>/pvc/welcomeAddPath.html
	Tunnel Server Address: <tunnel server address>

Create the v35 configuration file

Configuration information for the v35 must be added to a .json file that’s used when creating the v35. To create the configuration file:

  1. In a text editor, open the initial-config.json file downloaded earlier.
  2. Replace the placeholder text in the file as follows:
    • %%TIMEZONE%% - Specify a time zone string (for example, “America/Los_Angeles”). Use the time zone where the v35 will be located.
    • %%NTP_SERVER%% - An NTP server address (for example, “pool.ntp.org”). You can add additional NTP servers by separating them with commas.
    • %%NIS_ADDRESS%% - This is the “NIS Address:” value from the nis.config file downloaded from APM above.
    • %%SITE_KEY%% - This is the “Site Key:” value from the nis.config file downloaded from APM above.
    • %%TUNNEL_ADDRESS%% - This is the “Tunnel Server Address:” value from the nis.config file downloaded from APM above.
    • %%PLAINTEXT_PASSWORD%% - This is the password to configure for the v35 “admin” user.
  3. Save the file and exit the editor.

Create the v35

Once you have created the VM image and the configuration file, you can create the v35 VM itself:

./az-vm-create.sh -n <vm name> -c <config file>

Alternatively, if the export commands were not run in an earlier step:

./az-vm-create.sh -g <resource group name> -a <storage account> -n <vm name> -c <config file> [-b]

Command line options include:

  • -g <resource group name> - the name of your resource group
  • -a <storage account> - the name of the storage account associated with the resource group
  • -n <vm name> - the name to use for your v35 VM
  • -c <config file> - the name of the .json file containing your VM configuration

Optional command line options include:

  • -b - enables boot diagnostics and provides console access to the VM from Azure

When the script completes successfully, the output includes information about the v35 VM including its FQDN and public IP address.

{
  "fqdns": "<vm name>.<azure location>.cloudapp.azure.com",
  "id": "/subscriptions/<subscription number>/resourceGroups/<resource group name>/providers/Microsoft.Compute/virtualMachines/<vm name>",
  "location": "<azure location>",
  "macAddress": "<mac address>",
  "powerState": "VM running",
  "privateIpAddress": "<private IP>",
  "publicIpAddress": "<public IP>",
  "resourceGroup": "<resource group name>",
  "zones": ""
}

Note: Multiple v35 VMs can be created using the same <storage account> and <resource group name>.

Verify that you can access the v35

You can connect to the v35 Web Admin interface to confirm that it is running and that you can access it. To connect to the v35 Web Admin interface:

  1. In a web browser, enter the URL for the v35: https://<fqdns> (where <fqdns> is the FQDN returned when the v35 was created above). For example, if the VM name is “myv35” and Azure location is “eastus”, use: “https://myv35.eastus.cloudapp.azure.com”.
  2. Enter the v35 login credentials:
    • User ID = admin
    • Password = The password you entered in the configuration file for %%PLAINTEXT_PASSWORD%%.
      • You are logged onto the v35.

Configure for web proxy if required

If Internet traffic on your network is forwarded by a web proxy, you must configure the monitoring point with the proxy details.

Assign licenses

Every monitoring point is sold with a base license that allows it to monitor a certain number of applications. The base license must be assigned to the monitoring point in APM before it can be used. Optionally, add-on licenses can be assigned.

To license a monitoring point:

  1. Return to the browser tab where you are running APM.
  2. Navigate to > Manage Monitoring Points.
  3. Wait for the new monitoring point to show up in the list (you may need to refresh your screen).
    • The monitoring point status should show “Connection Established” ().
    • If it doesn’t appear after a few minutes, you’ll need to troubleshoot the problem.
  4. Assign a base license to the monitoring point.
  5. Optionally, assign add-on licenses as required.

Set the monitoring point location

When adding a new monitoring point to APM, you need to specify its location. This setting provides essential geographical context for the data that the monitoring point collects.

To set the location of the monitoring point:

  1. Enter the monitoring point location if prompted during the setup procedure.

Set up monitoring

At this point the monitoring point setup is complete. Continue the APM setup procedure at Set up monitoring.