Alibaba Cloud Express Connect
Collect Alibaba Cloud Express Connect monitoring data.
Configuration¶
Install Func¶
We recommend enabling Guance Integrations - Extensions - Hosted Func: all prerequisites are installed automatically. Continue with script installation.
To deploy Func yourself, see Self-hosted Func.
Enable the Script¶
Tip: Prepare the required Alibaba Cloud AK in advance (for simplicity, you can grant the global read-only permission
ReadOnlyAccess).
- Sign in to the Func console, click [Script Market], openGuanceScript Market, and search for
integration_alibabacloud_express_connect - Click Install, then enter the Alibaba Cloud AK ID, AK Secret, and account name.
- Click [Deploy Startup Script]. The system creates the
Startupscript set and configures the corresponding startup script automatically - Once enabled, view the trigger under Management / Automatic Trigger Configuration. Click [Run] to execute immediately without waiting for the schedule. After a short wait, view the execution records and logs
Verification¶
- Under [Management / Automatic Trigger Configuration], confirm that an automatic trigger configuration exists for the task, and check the task records and logs for errors.
- In Guance, check [Infrastructure / Custom] for asset information.
- In Guance, check [Metrics] for the corresponding monitoring data.
Before enabling monitors, verify that the actual data ingestion interval does not exceed the check window.
Metrics¶
After configuring Alibaba Cloud Monitoring, the default measurement is listed below. You can configure collection of additional metrics.
aliyun_acs_express_connect¶
| MetricName | MetricDescribe | Dimensions | Unit |
|---|---|---|---|
intranet_rx |
RI Inbound Bytes | instance_id, account_name, cloud_provider, user_id | B |
intranet_tx |
RI Outbound Bytes | instance_id, account_name, cloud_provider, user_id | B |
rate_limit_drop_pps |
RI Outbound Rate-Limit Packet Drop Rate | instance_id, account_name, cloud_provider, user_id | pps |
receive_bandwidth |
Inbound Bandwidth | instance_id, account_name, cloud_provider, user_id | bps |
router_interface_loss_rate_maximum |
RI Maximum Packet Loss Rate | instance_id, account_name, cloud_provider, user_id | percent |
rx_bandwidth_utilization |
Inbound Bandwidth Utilization | instance_id, account_name, cloud_provider, user_id | percent |
transported_bandwidth |
Outbound Bandwidth | instance_id, account_name, cloud_provider, user_id | bps |
tx_bandwidth_utilization |
Outbound Bandwidth Utilization | instance_id, account_name, cloud_provider, user_id | percent |
aliyun_acs_physical_connection¶
| MetricName | MetricDescribe | Dimensions | Unit |
|---|---|---|---|
bytes_in_from_idcto_vpc |
IDC to VPC Inbound Bytes | instance_id, access_point_id, vbr_id, vbr_name, account_name, region_id, cloud_provider, resource_group_id, user_id | B |
bytes_out_from_vpc_to_idc |
VPC to IDC Outbound Bytes | instance_id, access_point_id, vbr_id, vbr_name, account_name, region_id, cloud_provider, resource_group_id, user_id | B |
physical_connection_status_status |
Physical Connection Status | instance_id, access_point_id, account_name, physical_connection_id, physical_connection_name, region_id, cloud_provider, resource_group_id, user_id | status |
pkgs_drop_in_from_idcto_vpc |
IDC to VPC Inbound Dropped Packets | instance_id, access_point_id, vbr_id, vbr_name, account_name, region_id, cloud_provider, resource_group_id, user_id | count |
pkgs_drop_out_from_vpc_to_idc |
VPC to IDC Outbound Dropped Packets | instance_id, access_point_id, vbr_id, vbr_name, account_name, region_id, cloud_provider, resource_group_id, user_id | count |
pkgs_rate_limit_drop_out_from_vpc_to_vbr |
VPC to VBR Rate-Limit Dropped Packets | instance_id, access_point_id, vbr_id, vbr_name, account_name, region_id, cloud_provider, resource_group_id, user_id | count |
rate_in_from_idcto_vpc |
IDC to VPC Inbound Rate | instance_id, access_point_id, vbr_id, vbr_name, account_name, region_id, cloud_provider, resource_group_id, user_id | bps |
rate_out_from_vpc_to_idc |
VPC to IDC Outbound Rate | instance_id, access_point_id, vbr_id, vbr_name, account_name, region_id, cloud_provider, resource_group_id, user_id | bps |
Objects¶
The following is a physical connection object example. Replace values in angle brackets with actual resource information.
{
"measurement": "aliyun_physical_connection",
"tags": {
"account_name": "<Account Name>",
"physical_connection_id": "<Physical Connection ID>",
"physical_connection_name": "<Physical Connection Name>",
"region_id": "cn-hongkong",
"cloud_provider": "aliyun"
},
"fields": {
"bandwidth": 1000,
"status": "Enabled",
"business_status": "Normal",
"port_type": "10GBase-LR",
"product_type": "VirtualPhysicalConnection"
}
}
Note:tags,fields fields may change in later updates.