Azure Integration: Load Balancer Statistics

Introducion

8.8 comes with an AIP feature which allows to automatically distribute API calls across credentials that you should add to your Azure connection in ControlUp.

The maximum number of reading operations that can be performed on a credential at a subscription level is 12 000. Using only one credential can easily exhaust this limit in larger environments with many virtual machines or user sessions. You can read more about rate limits in the official Microsoft documentation.

Prerequisites

• ControlUp version 8.8 or higher

How to Identify Remaining Requests

The new AZ AIP Stats metric shows which credentials (service principals) are used to serve the communication with the corresponding Azure subscription. In the screenshot below you can see a number next to the Friendly Name of the service principal that calls the Azure API. This number represents the remaining read operations per credential.

You can see the percentage utilization of API calls at the subscription level with the AZ % Rate Limit Usage metric. For example, a displayed value of 40% means that 40% of available API calls are utilized, with 60% left. In the example below, we show you an automation example that you can use to get notified if this value crosses the critical threshold of 95%.

The AZ % AIP Variance is another important metric that is calculated as a percentage ratio of total remaining reads reduced by the lowest read count compared to the allowed read request count (usually 12 000).

Consider the scenario where two credentials are connected in ControlUp. The screenshot displays that one credential has 11,969 remaining requests while the other has 11,978.

Taken the maximum number of allowed read request of 12 000 this would be
(11 978 - 11 969) / 12 000 * 100 = 0.075 = 0.08%

Techniques to Mitigate API Rate Limitations

ControlUp will not be to request any further data from your Azure subscription once the request limit has been reached. Typically, there are two methods available to keep track of the request limit:

• Automatically trigger an action when AZ % Rate Limit Usage exceeds a certain threshold
• Monitor the AZ % Rate Limit Usage metric manually

Create Automated Actions

We recommend to set up an Advanced Trigger for the AZ % Rate Limit Usage column with a specified threshold of 95%. When this threshold is exceeded, it should activate a follow-up action, such as sending an email or Webhooks.