Huawei Cloud NAT Gateway
Collect monitoring metrics of Huawei Cloud NAT Gateway
Configuration¶
Install Func¶
It is recommended to activate TrueWatch Integration - Extensions - DataFlux Func (Automata): All prerequisites are automatically installed, please proceed with the script installation.
If deploying Func manually, refer to Deploy Func Manually
Install Script¶
Note: Please prepare Huawei Cloud AK with the required permissions in advance (for simplicity, you can grant global read-only permission
ReadOnlyAccess
)
-
Log in to the Func console, click 【Script Market】, enter the TrueWatch Script Market, and search for
integration_huaweicloud_nat
-
Click 【Install】, then enter the corresponding parameters: Huawei Cloud AK, SK, and account name
-
Click 【Deploy Startup Script】, the system will automatically create the
Startup
script set and configure the corresponding startup script -
After enabling, you can see the corresponding automatic trigger configuration in 「Manage / Automatic Trigger Configuration」. Click 【Execute】 to immediately execute once without waiting for the scheduled time. After a while, you can check the execution task records and corresponding logs
Verification¶
- In 「Manage / Automatic Trigger Configuration」, confirm whether the corresponding task has the corresponding automatic trigger configuration, and check the corresponding task records and logs for any exceptions
- In TrueWatch, 「Infrastructure - Resource Catalog」, check if there is asset information
- In TrueWatch, 「Metrics」, check if there is corresponding monitoring data
Metrics¶
Collect Huawei Cloud NAT Gateway metrics, more metrics can be collected through configuration Huawei Cloud NAT Gateway Metrics Details
Huawei Cloud NAT Gateway metrics are under the huaweicloud_SYS.NAT
measurement, below are the related metric descriptions
Metric ID | Metric Name | Metric Meaning | Value Range | Unit | Monitoring Period (Original Metric) |
---|---|---|---|---|---|
snat_connection |
SNAT Connection Count | This metric is used to count the SNAT connection count of the measurement object. | ≥ 0 | Count | 1 minute |
inbound_bandwidth |
Inbound Bandwidth | This metric is used to count the bandwidth from the public network to the current public NAT gateway instance. | ≥ 0 | bit/s | 1 minute |
outbound_bandwidth |
Outbound Bandwidth | This metric is used to count the bandwidth from the virtual private cloud to the current public NAT gateway instance. | ≥ 0 | bit/s | 1 minute |
inbound_pps |
Inbound PPS | This metric is used to count the PPS from the public network to the current public NAT gateway instance. | ≥ 0 | Count | 1 minute |
outbound_pps |
Outbound PPS | This metric is used to count the PPS from the virtual private cloud to the current public NAT gateway instance. | ≥ 0 | Count | 1 minute |
inbound_traffic |
Inbound Traffic | This metric is used to count the traffic from the public network to the current public NAT gateway instance. | ≥ 0 | Bytes | 1 minute |
outbound_traffic |
Outbound Traffic | This metric is used to count the traffic from the virtual private cloud to the current public NAT gateway instance. | ≥ 0 | Bytes | 1 minute |
snat_connection_ratio |
SNAT Connection Usage Ratio | This metric is used to count the SNAT connection usage ratio of the measurement object. The maximum connection count is the connection count limit of the specification. For details, see Product Specifications | ≥ 0 | % | 1 minute |
inbound_bandwidth_ratio |
Inbound Bandwidth Usage Ratio | This metric is used to count the inbound bandwidth usage ratio from the public network to the current public NAT gateway instance. | ≥ 0 | % | 1 minute |
outbound_bandwidth_ratio |
Outbound Bandwidth Usage Ratio | This metric is used to count the outbound bandwidth usage ratio from the virtual private cloud to the current public NAT gateway instance. | ≥ 0 | % | 1 minute |
total_inbound_udp_bandwidth |
Total Inbound UDP Bandwidth | This metric is used to count the total UDP bandwidth from the public network to the current public NAT gateway instance. | ≥ 0 | bit/s | 1 minute |
total_outbound_udp_bandwidth |
Total Outbound UDP Bandwidth | This metric is used to count the total UDP bandwidth from the virtual private cloud to the current public NAT gateway instance. | ≥ 0 | bit/s | 1 minute |
total_inbound_tcp_bandwidth |
Total Inbound TCP Bandwidth | This metric is used to count the total TCP bandwidth from the public network to the current public NAT gateway instance | ≥ 0 | bit/s | 1 minute |
total_outbound_tcp_bandwidth |
Total Outbound TCP Bandwidth | This metric is used to count the total TCP bandwidth from the virtual private cloud to the current public NAT gateway instance. | ≥ 0 | bit/s | 1 minute |
packets_drop_count_snat_connection_beyond |
Packet Drop Count (SNAT Connection Count Exceeded) | This metric is used to count the packet drop count caused by SNAT connection count exceeding the limit of the current public NAT gateway instance. | ≥ 0 | Count | 1 minute |
packets_drop_count_pps_beyond |
Packet Drop Count (PPS Exceeded) | This metric is used to count the packet drop count caused by PPS exceeding the limit of the current public NAT gateway instance. | ≥ 0 | Count | 1 minute |
packets_drop_count_eip_port_alloc_beyond |
Packet Drop Count (EIP Port Allocation Exceeded) | This metric is used to count the packet drop count caused by EIP port allocation exceeding the limit of the current public NAT gateway instance. | ≥ 0 | Count | 1 minute |
Objects¶
After data synchronization is normal, you can view the data in TrueWatch's 「Infrastructure - Resource Catalog」.
{
"measurement": "huaweicloud_nat",
"tags": {
"RegionId" : "cn-south-1",
"project_id" : "756ada1aa17e4049b2a16ea41912e52d",
"enterprise_project_id" : "0824ss-xxxx-xxxx-xxxx-12334fedffg",
"tenant_id" : "xxxxxx",
"instance_id" : "01fbb835-6b7f-41e9-842c-xxxxx0bc0s49e9",
"instance_name" : "nat-xxxx",
"status" : "aviable",
},
"fields": {
"router_id" : "xxxxxxxxx",
"description" : "xxxxxxxxx",
"internal_network_id" : "xxxxxxxxx",
"admin_state_up" : "xxxxx",
"created_time" : "2024-11-11T08:15:58Z",
"spec" : "xxxxx"
}
}
Note: The fields in
tags
,fields
may change with subsequent updates