Server Load Balancer provides a function that monitors the inbound and outbound traffic, number of maximum connections, and more. You can view real-time monitoring data on the console.
You are charged for the consumed network traffic from 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|| |
Monitoring data is collected each minute by the Server Load Balancer system, and forwarded to the cloud monitoring system. Then, the cloud monitoring system calculates the average value of all collected data in each 15 minutes.
The displayed network traffic data is the calculated average value.
Billing data is collected at the same granularity and accumulated to the billing system each hour in each bill cycle.
The monitoring data is the calculated average value, while the billing data is the accumulation value. These two data sets are not comparable because they are calculated and generated differently.
|Data observation|| |
Monitor provides the real-time data. However, a short delay may inevitably occur in the data collection, calculation, and display process.
Although this delay is almost insignificant, a delay creates a certain degree of discrepancy between the monitoring and billing data.
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 monitoring data is to help users observe if the instance has exceptions. If so, users can resolve the exceptions as soon as possible.
The purpose of billing data is to generate bills. Monitoring data cannot be used as the billing data.