CloudMonix hooks into Azure Management API to provide insight into the state and performance of Azure Virtual Network Gateways. Users can track and alert on connectivity, bandwidth (ingress/egress rate), and more. Both Classic and ARM APIs are supported.

In this article, we’ll highlight a couple of popular use cases where CloudMonix brings value to the monitoring of Azure Network Gateways.

To start monitoring Azure Virtual Network Gateways:

1. Run CloudMonix Setup Wizardto connect to your Azure environment

If you aren’t using CloudMonix yet,sign up for a free account, then authorize CloudMonix to view your Azure subscription with Azure Virtual Network. Learn more about the setup process here.

2. Monitor for connectivity issues

CloudMonix monitors statuses of all connections and raises an alert if any are not connected. This functionality is available by default, no special configuration necessary.

In some cases, it may be important to monitor and alert on a status of a particular connection within the Gateway. This can be achieved by following these steps:

Open the Azure Virtual Network Gateway configuration dialog.

Navigate to the “Alerts” tab to define a new alert verifying the state of a particular connection. The alert should be raised for the connection called “ABC” every time the state reported by CloudMonix is different from “Connected” (screenshot below): Any(ConnectionList, “LocalName == \”ABC\” && State != \”Connected\””)

Specify a sustained period for alert, e.g. 2 min. That will ensure alerts are not triggered prematurely due to temporary glitches.

3. Monitor Gateway throughput

Another important metric to monitor is the rate of incoming (ingress) and outgoing data (egress).

Note: CloudMonix tracks Ingress and Egress values by connection and across the gateway, as well as Ingress and Egress *rates* that are calculated as deltas between consecutive measurements of Ingress and Egress respectively. Thus, Egress and Ingress rate metrics are approximations.

Since Azure VN Gateways have a maximum throughput as defined during creation of the gateway, it may be beneficial to be alerted when the actual throughput comes close to or spikes above the maximum allowed limit. This can be done by adding Ingress and Egress rates.

To start monitoring the total data rate exchanged per gateway follow these steps:

Open the Azure Virtual Network Gateway configuration dialog.

Navigate to the “Metrics” tab to define a new metric “IngressRate” of type “AzureNetworkGatewayIngressRateBitsPerSec”, that will track the rate or incoming data(screenshot below).

Navigate to the “Metrics” tab to define a new metric “EgressRate” of type “AzureNetworkGatewayIngressRateBitsPerSec”, that will track the rate of outgoing data(screenshot below).

Navigate to the “Metrics” tab to define a new metric of type “DerivedMetric” that tracks the sum of EgressRate and IngressRate metrics (screenshot below).

Navigate to the “Alerts” tab to define a new alert that checks if the total throughput exceeds a threshold. Keep in mind that that Egress and Ingress rates can be reported by CloudMonix either in bytes/second or bits/second, so .

Screenshot below defines an alert that is raised when total throughput is over 80% of 100mbit/sec limit.

Specify a sustained period for alert, e.g. 2 min. That will ensure alert is not super sensitive to short-time spikes in throughput.

Apart from advanced monitoring and alerting CloudMonix allows also to automate common maintenance tasks and define self-healing actions. Read this article to learn how to automatically reboot VMs every day and read this article to see how to automatically restart crashed Windows Services.