- Product Introduction
- Purchase Guide
- Quick Start
- Operation Guide
- Cloud Monitoring Overview
- Monitoring View
- Dashboard
- Event Center
- Alarm Service
- Features
- Alarm Policy
- Alarm Notification
- Dynamic Threshold Alarm
- Configuring Trigger Condition Template
- Product Policy Type and Dimension Information
- Custom Message
- Viewing Alarm Records
- Configuring Alarm by Tag
- CVM Agents
- Cloud Access Management (CAM)
- CM Connection to Grafana
- Best Practice
- Tencent Cloud Service Metrics
- CVM
- CBS
- TencentDB
- TencentDB for SQL Server Monitoring API
- TencentDB for MySQL
- TencentDB for Redis
- TencentDB for MongoDB Monitoring Metrics
- TencentDB for PostgreSQL
- TencentDB for CYNOSDB_MYSQL Monitoring Metrics
- TencentDB for TcaplusDB Monitoring Metrics
- TencentDB for MariaDB Monitoring Metrics
- TDSQL for MySQL Monitoring Metrics
- TDSQL for MySQL Monitoring Metrics (Legacy)
- SCF
- CKafka
- VPC
- NAT Gateway Monitoring Metrics
- VPN Gateway Monitoring Metrics
- VPN Tunnel Monitoring Metrics
- Direct Connect Gateway Monitoring Metrics
- CCN Monitoring Metrics
- Peering Connection Monitoring Metrics
- Bandwidth Packet Monitoring Metrics
- EIP Monitoring Metrics
- Anycast EIP Monitoring Metrics
- Network Detection Monitoring Metrics
- CLB
- COS
- CFS
- CPM
- ECM
- EMR
- CDN
- Direct Connect
- TKE
- GAAP
- CMQ
- API Gateway
- Elasticsearch
- WAF
- Troubleshooting
- API Documentation
- History
- API Category
- Making API Requests
- Monitoring Data Query APIs
- Alarm APIs
- DescribeAlarmHistories
- CreateAlarmPolicy
- DeleteAlarmPolicy
- DescribeAlarmPolicies
- DescribeAlarmPolicy
- ModifyAlarmPolicyStatus
- SetDefaultAlarmPolicy
- BindingPolicyObject
- UnBindingPolicyObject
- UnBindingAllPolicyObject
- ModifyAlarmPolicyCondition
- ModifyAlarmPolicyNotice
- ModifyAlarmPolicyTasks
- DescribeMonitorTypes
- DescribeAllNamespaces
- DescribeAlarmMetrics
- DescribeAlarmEvents
- PutMonitorData
- DescribePolicyGroupInfo
- DescribeBindingPolicyObjectList
- DescribePolicyConditionList
- SendCustomAlarmMsg
- ModifyAlarmPolicyInfo
- Legacy Alarm APIs
- Notification Template APIs
- Event Center APIs
- Data Types
- Error Codes
- FAQs
- Notice
- Documentation Guide
- Product Introduction
- Purchase Guide
- Quick Start
- Operation Guide
- Cloud Monitoring Overview
- Monitoring View
- Dashboard
- Event Center
- Alarm Service
- Features
- Alarm Policy
- Alarm Notification
- Dynamic Threshold Alarm
- Configuring Trigger Condition Template
- Product Policy Type and Dimension Information
- Custom Message
- Viewing Alarm Records
- Configuring Alarm by Tag
- CVM Agents
- Cloud Access Management (CAM)
- CM Connection to Grafana
- Best Practice
- Tencent Cloud Service Metrics
- CVM
- CBS
- TencentDB
- TencentDB for SQL Server Monitoring API
- TencentDB for MySQL
- TencentDB for Redis
- TencentDB for MongoDB Monitoring Metrics
- TencentDB for PostgreSQL
- TencentDB for CYNOSDB_MYSQL Monitoring Metrics
- TencentDB for TcaplusDB Monitoring Metrics
- TencentDB for MariaDB Monitoring Metrics
- TDSQL for MySQL Monitoring Metrics
- TDSQL for MySQL Monitoring Metrics (Legacy)
- SCF
- CKafka
- VPC
- NAT Gateway Monitoring Metrics
- VPN Gateway Monitoring Metrics
- VPN Tunnel Monitoring Metrics
- Direct Connect Gateway Monitoring Metrics
- CCN Monitoring Metrics
- Peering Connection Monitoring Metrics
- Bandwidth Packet Monitoring Metrics
- EIP Monitoring Metrics
- Anycast EIP Monitoring Metrics
- Network Detection Monitoring Metrics
- CLB
- COS
- CFS
- CPM
- ECM
- EMR
- CDN
- Direct Connect
- TKE
- GAAP
- CMQ
- API Gateway
- Elasticsearch
- WAF
- Troubleshooting
- API Documentation
- History
- API Category
- Making API Requests
- Monitoring Data Query APIs
- Alarm APIs
- DescribeAlarmHistories
- CreateAlarmPolicy
- DeleteAlarmPolicy
- DescribeAlarmPolicies
- DescribeAlarmPolicy
- ModifyAlarmPolicyStatus
- SetDefaultAlarmPolicy
- BindingPolicyObject
- UnBindingPolicyObject
- UnBindingAllPolicyObject
- ModifyAlarmPolicyCondition
- ModifyAlarmPolicyNotice
- ModifyAlarmPolicyTasks
- DescribeMonitorTypes
- DescribeAllNamespaces
- DescribeAlarmMetrics
- DescribeAlarmEvents
- PutMonitorData
- DescribePolicyGroupInfo
- DescribeBindingPolicyObjectList
- DescribePolicyConditionList
- SendCustomAlarmMsg
- ModifyAlarmPolicyInfo
- Legacy Alarm APIs
- Notification Template APIs
- Event Center APIs
- Data Types
- Error Codes
- FAQs
- Notice
- Documentation Guide
Monitoring Metrics of a BM Private Network CLB Instance
Namespace
Namespace=QCE/BM_INTRA_LB
Monitoring Metrics
| Metric | Description | Unit |
|---|---|---|
| Inpkg | Inbound packets | Packets/sec |
| Outpkg | Outbound packets | Packets/sec |
| Intraffic | Inbound bandwidth | Mbps |
| Outtraffic | Outbound bandwidth | Mbps |
| Connum | Number of current connections (for the layer-4 listener) | - |
| Req | Number of requests (for the layer-7 listener) | - |
Note：
- The statistical granularity (
period) may vary for different metrics. You can obtain theperiodsupported by each metric by calling DescribeBaseMetrics.- You can query the monitoring metrics of a BM private network CLB instance from multiple dimensions. For more information, see Input Parameters.
Overview of Parameters in Each Dimension
| Parameter | Dimension Name | Dimension Description | Format |
|---|---|---|---|
| Instances.N.Dimensions.0.Name | vip | Dimension name of the CLB VIP | Enter a string-type dimension name, such as vip. |
| Instances.N.Dimensions.0.Value | vip | CLB VIP | Enter a specific IP address, such as 111.111.111.11. |
| Instances.N.Dimensions.1.Name | protocol | Dimension name of the protocol value | Enter a string-type dimension name, such as protocol. |
| Instances.N.Dimensions.1.Value | protocol | Protocol | Enter a specific protocol value, such as tcp. Possible values: tcp, udp, http, and https |
| Instances.N.Dimensions.2.Name | loadBalancerPort | Dimension name of the CLB port | Enter a string-type dimension name, such as loadBalancerPort. |
| Instances.N.Dimensions.2.Value | loadBalancerPort | CLB port | Enter a specific port number, such as 80. |
| Instances.N.Dimensions.3.Name | lanIp | Dimension name of the IP address of the real server | Enter a string-type dimension name, such as lanIp. |
| Instances.N.Dimensions.3.Value | lanIp | IP address of the real server | Enter a specific IP address, such as 11.22.33.44. |
| Instances.N.Dimensions.4.Name | rsPort | Dimension name of the port of the real server | Enter a string-type dimension name, such as rsPort. |
| Instances.N.Dimensions.4.Value | rsPort | Port of the real server | Enter a specific port number of the real server, such as 8080. |
| Instances.N.Dimensions.5.Name | vpcId | Dimension name of the integer ID of the VPC instance to which the CLB instance belongs | Enter a string-type dimension name, such as vpcId. |
| Instances.N.Dimensions.5.Value | vpcId | Integer ID of the VPC instance to which the CLB instance belongs | Enter a specific integer ID of the VPC instance to which the CLB instance belongs, such as 1. You can obtain the VPC ID from the vpcId field returned by the API for querying the VPC list. |
Input Parameters
BM private network CLB allows you to obtain the monitoring data at the following four levels:
CLB, listener, listener server, and listener server port.
1. To obtain the monitoring data at the CLB level, set the input parameters as follows:
&Namespace=QCE/BM_INTRA_LB
&Instances.N.Dimensions.0.Name=vip
&Instances.N.Dimensions.0.Value=
&Instances.N.Dimensions.1.Name=vpcId
&Instances.N.Dimensions.1.Value=
2. To obtain the monitoring data at the listener level, set the input parameters as follows:
&Namespace=QCE/BM_INTRA_LB
&Instances.N.Dimensions.0.Name=vip
&Instances.N.Dimensions.0.Value=
&Instances.N.Dimensions.1.Name=protocol
&Instances.N.Dimensions.1.Value=
&Instances.N.Dimensions.2.Name=loadBalancerPort
&Instances.N.Dimensions.2.Value=
&Instances.N.Dimensions.3.Name=vpcId
&Instances.N.Dimensions.3.Value=
3. To obtain the monitoring data at the listener server level, set the input parameters as follows:
&Namespace=QCE/BM_INTRA_LB
&Instances.N.Dimensions.0.Name=vip
&Instances.N.Dimensions.0.Value=
&Instances.N.Dimensions.1.Name=protocol
&Instances.N.Dimensions.1.Value=
&Instances.N.Dimensions.2.Name=loadBalancerPort
&Instances.N.Dimensions.2.Value=
&Instances.N.Dimensions.3.Name=lanIp
&Instances.N.Dimensions.3.Value=
&Instances.N.Dimensions.4.Name=vpcId
&Instances.N.Dimensions.4.Value=
4. To obtain the monitoring data at the listener server port level, set the input parameters as follows:
&Namespace=QCE/BM_INTRA_LB
&Instances.N.Dimensions.0.Name=vip
&Instances.N.Dimensions.0.Value=
&Instances.N.Dimensions.1.Name=protocol
&Instances.N.Dimensions.1.Value=
&Instances.N.Dimensions.2.Name=loadBalancerPort
&Instances.N.Dimensions.2.Value=
&Instances.N.Dimensions.3.Name=lanIp
&Instances.N.Dimensions.3.Value=
&Instances.N.Dimensions.4.Name=rsPort
&Instances.N.Dimensions.4.Value=
&Instances.N.Dimensions.5.Name=vpcId
&Instances.N.Dimensions.5.Value=
Yes
No
Was this page helpful?