Is there any limit to send/receive an API response service from windows Azure Virtual Machine?
As far as I know, there isn't any limit to send/receive an API response from Azure VM. The VM create in Azure, it works as a server same as a on-premises server.
About the Azure VMs limits, refer to the link.
The Azure VM's performance according to different VM size.
No, I think there isn't any limit as such. VMs are billed on capacity and no of hours run.
No limit, but you do need to pay for bandwidth after a certain point. Check here: https://azure.microsoft.com/en-us/pricing/details/bandwidth/.
The first 5 Gigabytes per month of outbound traffic are free.
After that you have to start paying something. Your VM will usually cost way more than the bandwidth (license, VM size, storage).
Related
I have a virtual machine on Azure and I was wondering if there is a bandwidth limit for it.
By bandwidth limit I mean, a limit like 15GB of outbound and inbound data transfer.
I tried checking some forums about this but could not find a clear answer.
Yes, as your VM will be on shared infrastructure, there are bandwidth limits for your VM. And the bandwidth is metered on egress (outbound) only and not on the ingress (inbound).
Further the bandwidth depends on your VM Size. The below link gives the network bandwidth limit of Dav4 and Dasv4-series
https://learn.microsoft.com/en-us/azure/virtual-machines/dav4-dasv4-series
For more information on Virtual Machine network bandwidth,
refer this link https://learn.microsoft.com/en-us/azure/virtual-network/virtual-machine-network-throughput
Hope this helps
I have a VM that runs IIS and SQL server for an enterprise application used by around 100 users.
Right now I just have this VM but I would like to add some availability. It’s not critical to have zero downtime application but at least that if by some reason the server fails then I’m able to wake up a secondary instance and reroute traffic to it.
So I guess this is done by using Availabilty Sets but what I understand is that I have at least to have two VMs in the availability set and load balancer so traffic is redirected round robin to each VM. By using the above approach that means that I must have to pay for having two instances with same specs I guess.
What I would like and don’t know if this is possible is like having same above scenario where one the of the VMs is stopped so I don’t get any charge and in case of VM failure I can started maybe manually so the application works again. If this is possible how does the hard drive is available so that the other VM always have the latest data.
If it’s not possible then can I have then for the availabilty set a second VM with the lowest specs that my app can support so if the main VM fails at least critical users can still access the app (maybe performance won’t be great but app will work) and when main VM is functional again then main traffic is again redirected to main VM.
you can achieve this by having 2 vms with premium disks only and having one as a cold backup. single vm qualify for an SLA if they only use premium disks, SLA would be 99.9% afair.
with AV sets - you need to have at least 2 running vms.
We have a Virtual machine on azure on which a web service is running. Since last few days there is constant over 1000 request from a single ip on the vm due to which the vm responds very slow or sometimes stop. Is there any feature in azure portal to limit the access of an ip address on vm after a limit or any other option?
Azure API Management is a managed service that allows you to throttle particular clients and also provides a lot of security and other features.
https://learn.microsoft.com/en-us/azure/api-management/api-management-key-concepts
I have been working on the Azure monitoring side for a while. I need your inputs for one of my requirement.
We have lot of IaaS VM’s both SQL and Non-SQL provisioned in our subscriptions. We are paying non-trivial amount for these VM’s. I am trying to come up w/ solution to identify low usage machines and during what times( night, early morning etc) the usage is very low. With this, I can take an action by either shut down VM’s during low usage period or reduce VM size.
For this, I am trying couple of options like Azure Advisor, Azure metrics for CPU usage, Network I/O, Disk Read/Write parameters. But considering only these might not help. Because, your network I/O might be having load balancer requests which cannot be considered.
So I need to come up w/ actual IIS requests went in during the given period.
Can you recommend on how to identify low usage VM’s? It would be a great help.
Can you recommend on how to identify low usage VM’s?
Generally, we will based on CPU usage to identify low usage VM.
Network traffic in or out of one application might be having load balancer requests, but network traffic in or out of this VM will not have load balancer, we also can use this to identify low usage VM.
So I need to come up w/ actual IIS requests went in during the given
period.
We can use OMS to monitor IIS request of each VMs in Azure, please follow this article to configure OMS.
like this:
Also we can config zabbix on one Azure VM and use that to monitor all VMs.
My WebServer VM is in different region and Database VM is in different region. For example, let's say WebServer VM is in Singapore, and Database VM is in US-West.
Now if I get a POST request from a user, which hits WebServer in Singapore region that inserts data into the database which is in US-West region, will this request be charged for outbound data transfer from webserver VM?
Thanks In Advance
Yes, the deployment as you described it would incur outbound data transfer charges. You would see some cost from the web server (making the call to the database), and some cost from the database server (results going back to the web server).
Here is the pricing page for Azure that explains data transfer rates. Notice that the rate varies by Zone. In your example, it would be between Zone 1 and Zone 2.
http://azure.microsoft.com/en-us/pricing/details/data-transfers/
Yes, all data outbound traffic is charged.
You also must take into consideration the latency caused by doing such a transaction, and the possible security issue in exposing your database on the Internet.