All Products
Search
Document Center

Virtual Private Cloud:Monitoring and O&M for VPC peering connections

Last Updated:Dec 12, 2024

You can use CloudMonitor to track metrics, such as traffic bandwidth and packet loss, for inter-region VPC peering connections. By setting up threshold alerts, you can monitor instance performance in real time and ensure business stability.

Overview

VPC peering connection monitoring

VPC peering connections connect two VPCs and enable communication between IPv4 and IPv6 traffic. After a peering connection is created, two VPCs in the same region or across regions can communicate with each other through private networks.

For inter-region VPC peering connections, you can Monitor traffic bandwidth and packet loss by clicking the icon icon.

Note

Monitoring metrics for intra-region VPC peering connections is currently not available.

Monitoring metrics

Monitoring data is available for time frames of 1 hour, 3 hours, 6 hours, 12 hours, or a custom period. The following table outlines the metrics being monitored:

Metric

Description

IntranetRX

The volume of data sent from the requester VPC to the accepter VPC within a given statistical period. Unit: bytes.

IntranetTX

The volume of data sent from the accepter VPC to the requester VPC within a given statistical period. Unit: bytes.

Inbound Bandwidth

The bandwidth from the requester to the accepter. Unit: bit/s.

Outbound Bandwidth

The bandwidth from the accepter to the requester. Unit: bit/s.

RateLimitDropPps

The rate of packet loss for outbound traffic that is discarded due to bandwidth limitations in the VPC peering connection. Unit: packets per second (pps).

CloudMonitor

You can use CloudMonitor to collect data, such as traffic bandwidth and packet loss, for VPC peering connections. CloudMonitor integrates application group management models and alert templates. You can create alert rules based on monitoring metrics and gain insights into the usage and status of your VPC peering connections.

Scenario

A company has created a peering connection to enable inter-region connectivity between VPC1 and VPC2. The traffic of the peering connection instance spiked to 100 MB within a short period, which potentially indicates a high traffic load on the deployed application or service. This could be due to normal business activity, a DDoS attack, crawler activity, or other network anomalies.

To monitor instances in real time and promptly identify and resolve network congestion or failures, the company uses CloudMonitor to collect traffic bandwidth metrics for the inter-region peering connection and creates threshold alert rules, thus helping reduce the O&M monitoring costs.

image

Procedure

Step 1: Create threshold alert rules

You can create threshold alert rules to monitor traffic bandwidth metrics of the peering connection in real time, ensuring business stability.

  1. Log on to the CloudMonitor console.

  2. In the left-side navigation pane, select Alerts > Alert Rules.

  3. On the Alert Rules page, click Create Alert Rule.

  4. In the Create Alert Rule panel, configure the parameters based on the following figure. You can keep other parameters at default values or adjust them as needed.

    The alert rule for this example is set as follows: An alert is triggered if the sum of inbound bandwidth for a consecutive period is ≥ 100 Mbit/s. A notification is sent if the sum for one consecutive period is ≥ 50 Mbit/s.

    When any of the threshold rules are triggered, CloudMonitor sends a corresponding alert based on the configurations. peer-view.png

Parameter description

Parameter

Description

Product

The name of the product managed by CloudMonitor.

Resource Range

The scope of the alert rule. Valid values:

  • All Resources: Applies to all resources of the cloud product and is effective for new resources.

  • Application Groups: Applies to all resources of a specified application group and is effective for new resources.

  • Instances: Applies to a specific resource.

Rule Description

The entity of the alert rule. When monitoring data meets the alert threshold, the alert rule is triggered.

Click Add Rule to set the rule name, metric type, monitoring metric, threshold, alert level, and alert method.

Mute For

The interval before the alert is sent again if it is not resolved.

Effective Period

The time during which the alert rule is effective. The alert rule only checks monitoring data within the effective period.

Alert Contact Group

The contact group to send alerts to.

Alert Callback

Enter a publicly accessible URL to which CloudMonitor will push alert information by using POST requests. Currently, only the HTTP protocol is supported.

Method to handle alerts when no monitoring data is found

Methods for handling alerts when there is no monitoring data. Valid values:

  • Do not do anything (Default)

  • Send alert notifications

  • Treated as normal

Step 2: Verify results

When the Inbound Bandwidth of the VPC peering connection exceeds 100 Mbit/s for one consecutive period:

image

The Alert Contact Group will receive a text message of the alert. You can view the alert history by clicking Alert History in the Actions column of Alert Rules.

image

References

  • For more information on monitoring metrics of CloudMonitor, see Metrics.

  • For more information on alert rule parameters and descriptions, see Alert rules.

  • You can manage alert rules through APIs, SDKs, Terraform, or ROS: