Metric Name | Metric Meaning |
CPU Utilization | CPU utilization of the AI gateway, calculated as the average based on the selected time granularity. |
Memory utilization | Memory utilization of the AI gateway, calculated as the average based on the selected time granularity. |
Inbound bandwidth traffic | Ingress bandwidth traffic of the AI gateway, calculated as the average based on the selected time granularity. |
Outbound bandwidth traffic | Egress bandwidth traffic of the AI gateway, calculated as the average based on the selected time granularity. |
TCP inbound connections | number of TCP connections of the AI gateway, calculated as the average based on the selected time granularity. |
Maximum Memory Utilization | Maximum memory utilization of the AI gateway within the selected time granularity. It is used to observe memory usage peaks and determine whether there is a risk of sudden memory increase (such as memory leak and burst traffic pressure). |
Maximum CPU Usage | Maximum CPU utilization of the AI gateway within the selected time granularity. It is used to discover CPU load peak fluctuations and locate performance surges caused by compute-intensive operations (such as complex authentication and protocol conversion). |
Number of Running Nodes | Number of normally running nodes in the AI gateway within the selected time granularity. It reflects the deployment scale and available node status. An abnormal decrease in the number of nodes may indicate a fault or scaling operation. |
New Connections from Client to Gateway Process | Number of newly established TCP connections between the client and the gateway process within the selected time granularity. It is used to observe the frequency of connection establishment over a short period and determine the activity level of client connections. |
Active Connections from Client to Gateway Process | Number of TCP connections in an active communication state between the client and the gateway process within the selected time granularity. It reflects the effective connection load currently borne by the gateway. |
Inactive Connections from Client to Gateway Process | Number of TCP connections that are established but have no active communication between the client and the gateway process within the selected time granularity. It assists in judging the idle status of connection resources. An excessive number may indicate that the connection reclamation / management mechanism needs optimization. |
Concurrent Connections from Client to Gateway Process | Total number of TCP connections that exist simultaneously between the client and the gateway process within the selected time granularity (including active and inactive). It directly reflects the concurrent connection pressure on the gateway and is a key metric for evaluating the connection capacity of the gateway. |
Inbound Traffic from Client to Gateway Process | Total data volume sent from the client to the gateway process within the selected time granularity. |
Outbound Traffic from Gateway Process to Client | Total data volume sent from the gateway process to the client within the selected time granularity. |
Inbound Bandwidth from Client to Gateway Process | Average bandwidth usage from the client to the gateway process within the selected time granularity (traffic transmission rate per unit time). It is used to evaluate the bandwidth pressure from the client to the gateway and avoid connection / transmission delays caused by bandwidth bottlenecks. |
Outbound Bandwidth from Gateway Process to Client | Average bandwidth usage from the gateway process to the client within the selected time granularity (traffic transmission rate per unit time). It is used in conjunction with "inbound bandwidth" to analyze the outbound bandwidth load of the gateway and prevent bandwidth bottlenecks from affecting response transmission. |
Metric Name | Metric Meaning |
Inbound traffic | The traffic from the client to the CLB within a statistical period. |
Outbound traffic | Traffic from CLB to the client within the statistical granularity |
Number of inbound packets | The number of data packets sent from the client to the CLB per second within a statistical period. |
Number of outbound packets | The number of data packets sent from the CLB to the client per second within a statistical period. |
Inbound bandwidth | Bandwidth used by traffic from the client to the CLB within a statistical period. |
Outbound bandwidth | Bandwidth used by traffic from the CLB to the client within a statistical period. |
Number of Active Connections | Number of active connections from the client to CLB within the statistical granularity |
Inactive connections | Number of inactive connections from the client to CLB within the statistical granularity |
Number of concurrent connections | Number of concurrent connections from the client to CLB within the statistical granularity |
New connections | Number of new connections from the client to CLB within the statistical granularity |
Metric Name | Metric Meaning |
Inbound bandwidth utilization | Utilization of bandwidth used by the client to access CLB through the public network within the statistical granularity |
Outbound bandwidth utilization | Utilization of bandwidth used by CLB to access the public network within the statistical granularity |
Concurrent connection utilization | Ratio of concurrent connections from the client to CLB at a specific moment within the statistical granularity to the maximum number of concurrent connections in the CLB specifications. |
New connection utilization | Ratio of new connections from the client to CLB within the statistical granularity to the maximum number of new connections in the CLB specifications |
Discarded connections. | Number of connections discarded by CLB within the statistical granularity |
Discarded inbound bandwidth | Discarded data when the client accesses CLB through the public network within the statistical granularity |
Discarded outbound bandwidth | Discarded data when CLB accesses the public network within the statistical granularity |
Discarded inbound packets | Number of data packets discarded when the client accesses CLB through the public network within the statistical granularity |
Discarded outbound packets | Number of data packets discarded when CLB accesses the public network within the statistical granularity |
Discarded QPS | Number of requests discarded by CLB within the statistical granularity |
QPS utilization | Ratio of QPS of CLB within the statistical granularity to the maximum QPS in the CLB specifications |
Metric Name | Metric Meaning |
Outbound traffic | Traffic from backend servers to CLB within the statistical granularity. |
Inbound bandwidth | Bandwidth used by traffic from the CLB to backend servers within a statistical period. |
Outbound bandwidth | Bandwidth used by traffic from backend servers to the CLB within a statistical period. |
Metric Name | Metric Meaning |
3xx status codes returned by CLB | Number of requests with status code 3xx returned by CLB within the statistical granularity (sum of codes returned by CLB and the gateway node) |
4xx status codes returned by CLB | Number of requests with status code 4xx returned by CLB within the statistical granularity (sum of codes returned by CLB and the gateway node) |
5xx status codes returned by CLB | Number of requests with status code 5xx returned by CLB within the statistical granularity (sum of codes returned by CLB and the gateway node) |
404 status codes returned by CLB | Number of requests with status code 404 returned by CLB within the statistical granularity (sum of codes returned by CLB and the gateway node) |
499 status codes returned by CLB | Number of requests with status code 499 returned by CLB within the statistical granularity (sum of codes returned by CLB and gateway node) |
502 status codes returned by CLB | Number of requests with status code 502 returned by CLB within the statistical granularity (sum of codes returned by CLB and the gateway node) |
503 status codes returned by CLB | Number of requests with status code 503 returned by CLB within the statistical granularity (sum of codes returned by CLB and the gateway node) |
504 status codes returned by CLB | Number of requests with status code 504 returned by CLB within the statistical granularity (sum of codes returned by CLB and the gateway node) |
2xx status codes | Number of requests with status code 2xx returned by the backend service within the statistical granularity. |
3xx status codes | Number of requests with status code 3xx returned by the backend service within the statistical granularity. |
4xx status codes | Number of requests with status code 4xx returned by the backend service within the statistical granularity. |
5xx status codes | Number of requests with status code 5xx returned by the backend service within the statistical granularity. |
404 status code | Number of requests with status code 404 returned by the backend service within the statistical granularity. |
499 status code | Number of requests with status code 499 returned by the backend service within the statistical granularity. |
502 status code | Number of requests with status code 502 returned by the backend service within the statistical granularity. |
503 status code | Number of requests with status code 503 returned by the backend service within the statistical granularity. |
504 status code | Number of requests with status code 504 returned by the backend service within the statistical granularity. |
Maximum request time | The maximum request time of the CLB within a statistical period. |
Average response time | The average response time of the CLB within a statistical period. |
Maximum response time | The maximum response time of the CLB within a statistical period. |
Number of response timeouts | The number of CLB response timeouts within a statistical period. |
Successful requests per minute | Number of successful requests of CLB within the statistical granularity |
Requests per second. | The number of requests per second of the CLB within a statistical period. |
Metric Name | Metric Meaning |
Number of Abnormal Health Checks | The number of CLB health check exceptions within a statistical period |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback