Alert when low in IP addresses and make block field optional

[jeevanions]

We use an internal tool which performs the IP allocation for us. One of the issues there is monitoring the available IP addresses.
It would be good to have email alerting when any of the blocks is running low in IP address.

The reason behind this; as part of the automation, we always use the same parameters hard coded for both space and block (both mandatory). In case the IP address runs out in the respective block, we need to update our automation to use a different block.

Can we make the block field optional so the IP address can be allocated from any of the blocks under the respective block?

[DCMattyG]

Ok @jeevanions, looks like two different asks here...

1. I believe it's possible to send out some kind of notification, but I'd like your input on the best way to handle this that would work across a broad range of users. Coding in SMTP support into the product is a poor choice and asking for a number of support nightmares. Another option may be creating an Event Grid and messaging out these type of events, or perhaps even connecting to an existing Event Grid. What are your thoughts?
2. In our upcoming code release, we have support for reservations at theSpace level, which allows you to add multiple Blocks from which to select a new CIDR from. Would that suffice for your use case (see screenshot below)?

[jeevanions]

@DCMattyG Regarding notification, I guess we can go with the Azure event hub. We use Dynatrace for monitoring, and our Azure services are integrated with it. I need to figure out how to get these events into Dynatrace. Another option is to send the metrics to Azure Monitor and set up some automated alert notifications (We can include it as part of bicep) so we make use of the Azure services for notification.

[jeevanions]

@DCMattyG Regarding making the block field optional, It would also help to make this field a list of blocks to cover other use cases. What do you think about this?

[DCMattyG]

Just to be clear, the above API does indeed accept a list of Blocks from which to choose a new CIDR. I think what you were implying was to additionally make specifying the list of blocks optional, and if this value was None/Null, then a CIDR would be chose from ANY of the Blocks within the Space....correct?