Server Load Balancer provides the monitoring function that monitors the inbound and outbound traffic, number of maximum connections and so on. You can view the real-time monitoring data on the console.
You are charged by the network traffic that the Server Load Balancer instance consumes. However, there are some differences between the monitoring data and the billing data, the differences are caused by the following factors as described in the table.
|Factors||Monitoring data||Billing data|
|Calculation methods|| |
The monitoring data is collected every one minute by the Server Load Balancer system, and passed to the cloud monitoring system. Then the cloud monitoring system calculates the average value of all collected data in every 15 minutes.
The displayed network traffic data is the calculated average value.
The billing data is collected at the same granularity and is accumulated to the billing system every one hour in each bill cycle.
The monitoring data is the calculated average value, while the billing data is the accumulation value. Because these two data sets are calculated and generated differently, they are not comparable.
|Real time|| |
The Monitor function provides the real-time data. However, a short delay may occur inevitably in the data collection, calculation and display process.
Although this delay is small, it still results in a certain degree of discrepancy between the monitoring and the billing data.
The billing data tolerates a maximum delay of three hours. For example, billing data generated between 01:00-02:00 will be reported by 05:00. Therefore, the billing data is different from the monitoring data.
The purpose of the monitoring data is to help users to observe if the instance has exceptions. If so, users can resolve the exceptions as soon as possible.
The purpose of billing data is used to generate bills. The monitoring data cannot be used as the billing data.