Azure Virtual Network (VNet) monitoring integration
Azure Virtual Network (VNet) allows your Azure Virtual Machines (VMs) and other Azure resources to communicate among themselves, with the internet, and with other on-premises networks.
Site24x7's Azure Virtual Network (VNet) integration lets you monitor Azure Virtual Network, configure thresholds, and receive alerts about critical issues.
Table of contents
Setup and Configuration
- Adding Azure Virtual Network (VNet) while configuring a new Azure monitor
If you haven't configured an Azure monitor yet, add one by following the steps below:
- Log in to your Site24x7 account.
- Go to Cloud > Azure > Add Azure Monitor. You can also follow these steps to add an Azure monitor.
- During Azure monitor configuration, on the Edit Azure Monitor page, select Virtual Network (VNet) from the Service/Resource Types drop-down.
- Adding Virtual Network (VNet) to an existing Azure monitor
If you already have an Azure monitor configured for the tenant, you can add Azure Virtual Network (VNet) by following the steps below:
- Log in to your Site24x7 account.
- Go to Cloud > Azure, select your Azure monitor, then go to any of the dashboards on the left pane of your Azure monitor.
- Click the hamburger icon and select Edit, which brings you to the Edit Azure Monitor page.
- On the Edit Azure Monitor page, select the corresponding Subscriptions and Resource Groups from the drop-down, select Azure Virtual Network (VNet) from the Service/Resource Types drop-down, and click Save.
- After successful configuration, go to Cloud > Azure > Azure Monitor > Azure Virtual Network (VNet). Now you can view the discovered Azure Virtual Network (VNet).
Polling frequency
Site24x7's Azure Virtual Network (VNet) service monitor collects metric data every five minutes and displays the minute-by-minute status.
Supported metrics
Metric name | Description | Statistic | Unit |
---|---|---|---|
Round trip time for Pings to a VM | The time taken by pings sent to a destination VM for a round trip | Average | Milliseconds |
Failed Pings to a VM | The percentage of failed pings out of the total pings sent to a destination VM | Average | Percent |
Inbound packets DDoS | The total number of in-bound DDoS packets | Maximum | Count per second |
Inbound packets dropped DDoS | The total number of dropped in-bound DDoS packets | Maximum | Count per second |
Inbound packets forwarded DDoS | The total number of in-bound DDoS packets allowed to pass through | Maximum | Count per second |
Inbound TCP packets DDoS | The total number of in-bound TCP DDoS packets | Maximum | Count per second |
Inbound TCP packets dropped DDoS | The total number of dropped in-bound TCP DDoS packets | Maximum | Count per second |
Inbound TCP packets forwarded DDoS | The total number of in-bound TCP DDoS packets allowed to pass through | Maximum | Count per second |
Inbound UDP packets DDoS | The number of in-bound UDP DDoS packets | Maximum | Count per second |
Inbound UDP packets dropped DDoS | The total number of dropped in-bound UDP DDoS packets | Maximum | Count per second |
Inbound UDP packets forwarded DDoS | The total number of in-bound UDP DDoS packets allowed to pass through | Maximum | Count per second |
Inbound bytes DDoS | The total size of in-bound DDoS packets | Maximum | Bytes per second |
Inbound bytes dropped DDoS | The total size of dropped in-bound DDoS packets | Maximum | Bytes per second |
Inbound bytes forwarded DDoS | The total size of in-bound DDoS packets allowed to pass through | Maximum | Bytes per second |
Inbound TCP bytes DDoS | The total size of in-bound TCP DDoS packets | Maximum | Bytes per second |
Inbound TCP bytes dropped DDoS | The total size of dropped in-bound TCP DDoS packets | Maximum | Bytes per second |
Inbound TCP bytes forwarded DDoS | The total size of in-bound TCP DDoS packets allowed to pass through | Maximum | Bytes per second |
Inbound UDP bytes DDoS | The total size of in-bound UDP DDoS packets | Maximum | Bytes per second |
Inbound UDP bytes dropped DDoS | The total size of dropped in-bound UDP DDoS packets | Maximum | Bytes per second |
Inbound UDP bytes forwarded DDoS | The total size of in-bound UDP DDoS packets allowed to pass through | Maximum | Bytes per second |
Under DDoS attack or not | Shows if a DDoS attack is happening or not | Maximum | Count |
Inbound TCP packets to trigger DDoS mitigation | Shows if DDoS mitigation was triggered by in-bound TCP packets | Maximum | Count per second |
Inbound UDP packets to trigger DDoS mitigation | Shows if DDoS mitigation was triggered by in-bound UDP packets | Maximum | Count per second |
Inbound SYN packets to trigger DDoS mitigation | Shows if DDoS mitigation was triggered by in-bound SYN packets | Maximum | Count per second |
Licensing
Azure Virtual Network (VNet) consumes one basic monitor.
Threshold configuration
- Global configuration
- In the Site24x7 web client, go to the Admin section on the left navigation pane.
- Select Configuration Profiles from the left pane and select Threshold and Availability (+) from the drop-down.
- Click Add Threshold Profile on the top-right corner of the page.
- In the Monitor Type drop-down select Azure Virtual Network (VNet).
- Now you can set the threshold values for all the metrics mentioned above.
- Monitor-level configuration
- In the Site24x7 web client, go to Cloud > Azure > Azure Monitor > Azure Virtual Network (VNet).
- Select the resource you would like to set a threshold for, then click the hamburger icon.
- Select Edit, which directs you to the Edit Azure Virtual Network (VNet) page.
- You can set the threshold values for the metrics by selecting Threshold and Availability.
- You can also configure IT Automation at the attribute level.
IT Automation
Site24x7's IT Automation tools help automatically resolve performance degradation issues. The alarm engine continually evaluates system events for which thresholds are set and executes the mapped automation when there is a breach.
How to configure IT Automation for a monitor
Configuration Rules
Configuration Rules can be applied to all monitor types in Site24x7. Rules can be configured and associated with existing monitors. Additionally, when a new monitor is being added, you can run a check, and associate any of the previously created rules that match the monitor configurations.
How to add a Configuration Rule
Summary
The Summary tab will give you the performance data organized by time for the metrics listed above.
- To view the summary, go to Cloud > Azure > Azure Monitor > Azure Virtual Network (VNet).
- Select a resource and click the Summary tab.
- By doing so, you can view the above metrics.
Configuration Details
The configuration details of an Azure Virtual Network (VNet) resource are provided under the Configuration Detailstab.
- To get the configuration details, go to Cloud > Azure > Azure Monitor > Azure Virtual Network (VNet).
- Click a resource and select the Configuration Details tab.
Reports
Gain in-depth data about the various parameters of your monitored resources and highlight your service performance using our insightful reports.
To view reports for Azure Virtual Network (VNet):
- Go to the Reports section on the left navigation pane.
- Select Azure Virtual Network (VNet) from the menu on the left.
- You can find the Availability Summary Report, Performance Report, and Inventory Report for one selected monitor, or you can get the Summary Report, Availability Summary Report, Health Trend Report, and Performance Report for all the Azure Virtual Network (VNet).
You can also get reports from the Summary tab of the Azure Virtual Network (VNet) monitor.
Click the Summary tab of the Azure Virtual Network (VNet) monitor and get the Availability Summary Report of the monitor by clicking Availability or Downtime. You can also find the Performance Report of the monitor by clicking any chart title.