Start monitoring IP address capacity¶

Available since MOSK 25.1

Note

The MOSK deployments with Tungsten Fabric do not support IP address capacity monitoring.

Monitoring IP address capacity helps cloud operators allocate routable IP addresses efficiently for dynamic workloads in the clouds. This capability provides insights for predicting future needs for IP addresses, ensuring seamless communication between workloads, users, and services while optimizing IP address usage.

By monitoring IP address capacity, cloud operators can:

Predict when to add new IP address blocks to prevent service disruptions.
Identify networks or subnets nearing capacity to prevent issues.
Optimize the allocation of costly external IP address pools.

To start monitoring IP address capacity in your cloud:

Verify that all required networks and subnets are monitored.

By default, MOSK monitors IP address capacity for the external networks that have the router:external=External attribute and segmentation type of vlan or flat.

To include additional networks and subnets in the monitoring:
- Tag the network with the openstack.lcm.mirantis.com:prometheus tag. When a network is tagged, all its subnets are automatically included in the monitoring:
```
openstack network set <NETWORK-ID> --tag openstack.lcm.mirantis.com:prometheus
```
- Tag individual subnets with the openstack.lcm.mirantis.com:prometheus tag. This includes the subnet in the monitoring regardless of the network tagging:
```
openstack subnet set <SUBNET_ID> --tag openstack.lcm.mirantis.com:prometheus
```
View and analyze the monitoring data.

The metrics of IP address capacity are collected by the OpenStack Exporter and are available in Prometheus within the StackLight monitoring suite as:
- osdpl_neutron_network_total_ips
- osdpl_neutron_network_free_ips
- osdpl_neutron_subnet_total_ips
- osdpl_neutron_subnet_free_ips