tencent cloud

Tencent Cloud Observability Platform

Release Notes and Announcements
Release Notes
Product Introduction
Overview
Strengths
Basic Features
Basic Concepts
Use Cases
Use Limits
Purchase Guide
Tencent Cloud Product Monitoring
Application Performance Management
Mobile App Performance Monitoring
Real User Monitoring
Cloud Automated Testing
Prometheus Monitoring
Grafana
EventBridge
PTS
Quick Start
Monitoring Overview
Instance Group
Tencent Cloud Product Monitoring
Application Performance Management
Real User Monitoring
Cloud Automated Testing
Performance Testing Service
Prometheus Getting Started
Grafana
Dashboard Creation
EventBridge
Alarm Service
Cloud Product Monitoring
Tencent Cloud Service Metrics
Operation Guide
CVM Agents
Cloud Product Monitoring Integration with Grafana
Troubleshooting
Practical Tutorial
Application Performance Management
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Parameter Information
FAQs
Mobile App Performance Monitoring
Overview
Operation Guide
Access Guide
Practical Tutorial
Tencent Cloud Real User Monitoring
Product Introduction
Operation Guide
Connection Guide
FAQs
Cloud Automated Testing
Product Introduction
Operation Guide
FAQs
Performance Testing Service
Overview
Operation Guide
Practice Tutorial
JavaScript API List
FAQs
Prometheus Monitoring
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Terraform
FAQs
Grafana
Product Introduction
Operation Guide
Guide on Grafana Common Features
FAQs
Dashboard
Overview
Operation Guide
Alarm Management
Console Operation Guide
Troubleshooting
FAQs
EventBridge
Product Introduction
Operation Guide
Practical Tutorial
FAQs
Report Management
FAQs
General
Alarm Service
Concepts
Monitoring Charts
CVM Agents
Dynamic Alarm Threshold
CM Connection to Grafana
Documentation Guide
Related Agreements
Application Performance Management Service Level Agreement
APM Privacy Policy
APM Data Processing And Security Agreement
RUM Service Level Agreement
Mobile Performance Monitoring Service Level Agreement
Cloud Automated Testing Service Level Agreement
Prometheus Service Level Agreement
TCMG Service Level Agreements
PTS Service Level Agreement
PTS Use Limits
Cloud Monitor Service Level Agreement
API Documentation
History
Introduction
API Category
Making API Requests
Monitoring Data Query APIs
Alarm APIs
Legacy Alert APIs
Notification Template APIs
TMP APIs
Grafana Service APIs
Event Center APIs
TencentCloud Managed Service for Prometheus APIs
Monitoring APIs
Data Types
Error Codes
Glossary

Monitoring Metrics of a BM Public Network CLB Instance

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-10-27 18:55:51

Namespace

Namespace=QCE/BM_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 (Layer-4 listener)
-
Req
Number of requests (Layer-7 listener)
-
Note:
The statistical granularity (period) may vary by metrics. You can obtain the period supported by each metric by calling the DescribeBaseMetrics API.
You can query the monitoring metrics of BM public network CLB in 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 value
Enter a specific protocol value, such as tcp
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 it from the vpcId field returned by the qDescribeVpcs API

Input Parameters

To query the monitoring data of the BM public network CLB instance, configure input parameters as follows:
BM public network CLB allows you to obtain monitoring data at the following four levels: CLB, listener, listener server, and listener server port.
1. To obtain monitoring data at the CLB level, configure input parameters as follows:
&Namespace=QCE/BM_LB &Instances.N.Dimensions.0.Name=vip &Instances.N.Dimensions.0.Value=VIP of the CLB instance
2. To obtain monitoring data at the listener level, configure input parameters as follows:
&Namespace=QCE/BM_LB &Instances.N.Dimensions.0.Name=vip &Instances.N.Dimensions.0.Value=VIP of the CLB instance &Instances.N.Dimensions.1.Name=protocol &Instances.N.Dimensions.1.Value=Protocol value &Instances.N.Dimensions.2.Name=loadBalancerPort &Instances.N.Dimensions.2.Value=Port of the CLB instance
3. To obtain monitoring data at the listener server level, configure input parameters as follows:
&Namespace=QCE/BM_LB &Instances.N.Dimensions.0.Name=vip &Instances.N.Dimensions.0.Value=VIP of the CLB instance &Instances.N.Dimensions.1.Name=protocol &Instances.N.Dimensions.1.Value=Protocol value &Instances.N.Dimensions.2.Name=loadBalancerPort &Instances.N.Dimensions.2.Value=Port of the CLB instance &Instances.N.Dimensions.3.Name=lanIp &Instances.N.Dimensions.3.Value=IP address of the real server &Instances.N.Dimensions.4.Name=vpcId &Instances.N.Dimensions.4.Value=Integer ID of the VPC instance to which the CLB instance belongs
4. To obtain monitoring data at the listener server port level, configure input parameters as follows:
&Namespace=QCE/BM_LB &Instances.N.Dimensions.0.Name=vip &Instances.N.Dimensions.0.Value=VIP of the CLB instance &Instances.N.Dimensions.1.Name=protocol &Instances.N.Dimensions.1.Value=Protocol value &Instances.N.Dimensions.2.Name=loadBalancerPort &Instances.N.Dimensions.2.Value=Port of the CLB instance &Instances.N.Dimensions.3.Name=lanIp &Instances.N.Dimensions.3.Value=IP address of the real server &Instances.N.Dimensions.4.Name=rsPort &Instances.N.Dimensions.4.Value=Port of the real server &Instances.N.Dimensions.5.Name=vpcId &Instances.N.Dimensions.5.Value=Integer ID of the VPC instance to which the CLB instance belongs

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック