This article introduces how to use the monitoring feature to view CLB private or public traffic and how to configure alarm policies to track traffic usage in time.

Application scenarios

In businesses using CLB for access traffic distribution, monitoring CLB traffic usage or configuring inbound and outbound bandwidth alarm policies for CLB helps to track business traffic promptly and prevent issues caused by excessive traffic.

Traffic usage of public CLB and private CLB with associated EIP can be understood by viewing CLB or EIP traffic usage within a specific period. Traffic usage of private CLB without associated EIP can be understood by viewing CLB traffic usage within a specific period.

After configuring inbound and outbound bandwidth alarm policies for CLB, manual periodic checks are unnecessary. When bandwidth reaches a certain value, an alarm triggers and notifies contacts via email or SMS, enabling timely adjustments and avoiding business issues due to excessive traffic.

Prerequisites

Completed creation of alarm contacts and contact group (alarmgroup-test). Procedure can be found increating alarm contacts and contact groups.

Instance suspension or upgrade may cause no data in CLB monitoring metrics for some time; ensure CLB has been running normally for a while before checking.

View traffic usage

View CLB usage traffic

View internet IP usage traffic

log in to the CLB console.

In the top menu bar, select the target project and region.

Click the target CLB instance name.

On the Monitoring tab, click the Instance or Listener tab, and select a time period, for example, 1 day.

View the inbound and outbound bandwidth statistics of an instance or a listener.

tip

More CLB monitoring metrics are available inCLB monitoring metrics.

Configuring an alarm strategy

The following uses configuring an instance alarm strategy as an example; configuring a listener alarm strategy follows similar steps.

Log in to the CloudMonitor console.

In the left-side navigation pane, select Alert Center > Alert policy.

On the alert policy page, click the Create alert policy button.

Configure the basic alarm information, and set the policy name to policy-clb.

Refer to the table below to configure alert objects.

Parameter	Value
Resource Type	Classic Load Balancer
Regions	China (Beijing)
Dimension	Instance
Resource	All tip If you select All, the alarm policy takes effect on all instances in the current region. If you select Part, you need to further select the instances on which the alarm policy takes effect.

Refer to the table below to configure alert rules.

Parameter	Value
Metric type	Single metric
Trigger condition	Inbound bandwidth average over 3 consecutive cycles (1 cycle = 1 minute) > 30 Mbit/s tip This trigger condition means CloudMonitor checks the inbound bandwidth of the Cloud Load Balancer instance every minute and triggers an alert when the average exceeds 30 Mbit/s for 3 consecutive times.
Alarm level	Warning
Effective on	00:00-23:59
Alarm sending period	5 minutes

Configure notification methods for the alarm policy.

Alarm channel set to email, Alarm contact group set to alarmgroup-test.

Click OK.

Load Balancer