Azure Subnet Monitoring | Cloudmon

Azure Subnet

Microsoft Azure

Azure Subnet

Discover the subnets in your connected Azure account, see each one with the virtual network it belongs to, its address prefix, and its connected devices, and track the health and performance measures Azure Monitor provides.

Overview

A subnet is a range of IP addresses within an Azure virtual network. Resources placed in a subnet take their addresses from that range.

Cloudmon automatically discovers the subnets in your connected Azure account. Navigate to Cloud → Azure → [Select Account] → Azure Subnet to view the list.

To connect an Azure account, see How to Set Up Azure Monitoring.

Turning On Monitoring for Azure Subnet

The Services tab of the Azure account shows a card for each Azure service. Select All to see every supported service. A service that is not yet monitored for the account shows an Enable button instead of a resource count.

To choose the services discovered for an account, edit the account and select them under Services to be Discovered, as described in Actions in Azure Monitoring.

Azure Subnet List

The list displays all discovered subnets with the following details:

ColumnDescription
NameThe name of the resource as configured in Azure.
Resource GroupThe resource group the resource belongs to.
LocationThe Azure region where the resource is deployed.
Virtual NetworkThe virtual network that contains the subnet.
Address PrefixThe address range of the subnet, in CIDR notation.
Connected DevicesThe devices connected to the subnet.
StatusThe current status of the resource.
ActionsOptions for managing monitoring of the resource.

IP Address Usage

Azure does not publish performance metrics for subnets. The key measure is IP address usage: Azure reports, for each subnet, how many addresses are in use compared with the size of the subnet.

MetricDescription
Subnet size and usageHow many IP addresses in the subnet are in use, compared with the size of the subnet.

Use Cases

  • Watch IP usage so a subnet is resized or split before it runs out of addresses and new resources fail to deploy.

Troubleshooting

IssueWhat to check
The list shows "There are no Azure Subnet Available"The account has no VPN gateways, or discovery has not run since they were created. Navigate to Cloud → Azure → [Account], open the menu (☰), and click Rediscover.
The service card shows EnableThe service is not monitored for this account. Edit the account and select Azure Subnet under Services to be Discovered.
Resources are missing after discoveryConfirm that the application registered for Cloudmon has the Reader role on the subscriptions that contain the resources. See How to Set Up Azure Monitoring.