Hi,
I was wondering why there are separate monitor types for monitoring VMs in Azure.
It is confusing and adds significant cost to have both.
When I look at AWS the EC2 instance monitor includes the server metrics as an additional tab.
Why has this not been done for Azure and are there plans to fix this?
I also see that the EC2 monitors have quite a bit more detail on configuration than the Azure monitors.
Does anyone from Site24x7 have any insights?
Some basic calculations
Example:
Azure
Environment:
7 VMs.
1 Network interface per VM
1 OS disk per VM
1 data disk per VM
When the monitors get added to Site24x7 for one VM we get
1 VM monitor
1 Server monitor
1 network interface
2 disks
For a total of 5 monitors for 1 VM.
Multiply that by 7 and you get 35.
Example for AWS
7 VMs
1 Network interface per VM
1 OS disk per VM
1 data disk per VM
When added/discovered we get
1 EC2 monitor for each VM which has the network,server and related info.
Total monitors =7
Dear Herb,
Let me explain your questions
>>> When I look at AWS the EC2 instance monitor includes the server metrics as an additional tab.
This is available in Azure VM monitor as well. When you install the server agent, additional tabs are added in the Azure VM monitor itself. You can install the agent using VM Extensions , using the ARM template or by using other deployment tools.
As for the calculations you have given, I understand the disparity between the two. We are on it to make it uniform across clouds.
-Jasper