Application Insights is a Service on Microsoft Azure that lets you understand what users are actually doing on your App. It also lets you diagnose any issues with it’s Powerful analytics tools and works with platforms including .Net, Java and Node.js.
The App Insights Instrumentation key is what is required to link your App with the resource on Azure. If you already have an existing App Insights resource created through Visual Studio and you need to change it, then you can create another resource manually from the Azure Portal.
Once the App Insights resource is created, copy the Instrumentation key and replace it in your ApplicationInsights.config file. This lets you switch the ApplicationInsights resource for your Application.
Start debugging your App and verify with your Live Metrics Stream in the App Insights resource that it is working.
Currently I’ve setup the Ubuntu Server 18.04 LTS from the Azure marketplace and I’m trying to access it via VNC Server setup on the Linux machine. Also, you’ll need a vnc client like RealVNC or you can also use the screen-sharing client available on your Mac.
First you need to login to your Linux VM as a non-root user which you’ve created while setting up the VM. To spin up a new Linux VM, you can check out this post. You can use the Cloud shell to connect to your VM using the non-root username and password to your machine via SSH. Use the Connect menu of your VM and copy the SSH command to run in the Cloud shell.
You just need to replace the your_user_name and IP_Address parts in the above command. Enter the password you’re prompted for to complete the Login as SSH.
Install the required packages:
We now need to install the required packages like Xfce desktop environment and VNC Server which are not bundled in the Ubuntu OS by default. Xfce is a free and open-source desktop environment for Unix and Unix like Operating Systems.
Update list of packages:
$ sudo apt update
Install Xfce Desktop environment and wait for the installation to complete:
$ sudo apt install xfce4 xfce4-goodies
Install the VNC Server:
$ sudo apt install tightvncserver
Complete the initial configuration and provide the setup password:
Providing a view-only password is optional. You’ll get the below Output as the initial configuration completes:
Creating default startup script /home/your_user_name/.vnc/xstartup Starting applications specified in /home/your_user_name/.vnc/xstartup Log file is /home/your_user_name/.vnc/your_hostname:1.log
Configure VNC Server:
The VNC Server is by default configured on the port 5901 and display port :1. VNC can launch multiple instances on other ports like :2, :3 and so on.
Let’s first kill the current instance for further configuration that we require:
$ vncserver -kill :1
Killing Xtightvnc process ID <ID>
Backup the xstartup file before modifying:
$ mv ~/.vnc/xstartup ~/.vnc/xstartup.bak
Create a new xstartup file and open in editor:
$ nano ~/.vnc/xstartup
Add the following lines to your file in the nano editor and save it:
I’ll be using the Azure portal UI to create a marketplace image for Ubuntu Linux. Some of the UI features may change in future, but the crux will remain pretty much similar more or less.
Open Marketplace for VM Images on Azure portal
Fill up the VM Image details
Create or select Resource Group.
Give a suitable name.
Select region based on your geographic availability.
For personal use redundancy is not required. You can change Availability options based on Availability Zone or Availability set.
Select the Marketplace image for the available Ubuntu version.
Select a machine size based on vcpus, memory and IOPS requirement. Of course, check the cost factor.
Setup Authentication using Password or SSH public key
You can simply use Username and Password for authentication otherwise use SSH public/private key pair.
For generating SSH public key, use Putty gen for Windows or ssh-keygen on Linux and OSX. You can download a suitable Putty client for windows here.
Generate RSA 2048-bit key and follow the instructions by the tool.
Save the Private key file as .ppk
Save the Public key file as .pub
Export the Private key file as .openssh format using the Conversions menu if this key will be used by an external SSH client such as on Linux.
For the Admin account, put a suitable Username and SSH public key generated above starting with “ssh-rsa” as shown below. Make sure the key is copied as is without any modifications.
Add Disks information
It’s better to use Premium SSD for optimal performance. If you have additional disks already created you can attach it with the VM at this step or you can also do this later.
This step creates a Virtual Network, a subnet and a Public IP for the VM. All these are added to the same Resource Group while creating these new resources. You can also select if you have these existing resources.
Allow Inbound Ports
You can select the required ports e.g. SSH for connecting using SSH public/private key-pair or RDP to connect using Username and Password.
Keep these to default if you prefer. You can enable/disable any option based on requirement. I turned off Boot diagnostics as it required to create a Storage account so I switched it off, as I don’t require it for a test VM.
You can provide additional post-deployment configuration options using extensions like chef and puppet or Cloud init for Linux.
You can add various tags to categorize resources for consolidated billing and automation management.
Review your provided details in the next step and click on Create. Wait for the deployment to succeed.
Accessing the VM
For accessing the VM, check if you have inbound port rules set up to access using Public IP address with RDP or SSH. Use Putty configuration client to SSH into the VM using port 22 on Windows machine. From a Unix like system including MacOS, use the following command:
ssh <username>@<computer name or IP address>
For details on how to connect to your Ubuntu Linux VM from your Mac machine, check out this post.