Monitoring Metrics

Overview

This section describes the namespace, the metrics that can be monitored by Cloud Eye, and dimensions of these metrics. You can use APIs provided by Cloud Eye to query the metrics of a monitored object and generated alarms.

Namespace

SYS.ELB

Metrics

Table 1 Metrics supported by ELB
Metric ID	Name	Description	Value	Monitored Object	Monitoring Period(Raw Data)
m1_cps	Concurrent Connections	Load balancing at Layer 4: total number of TCP and UDP connections from the monitored object to backend servers Load balancing at Layer 7: total number of TCP connections from the clients to the monitored object Unit: N/A	≥ 0	Dedicated load balancer Shared load balancer Dedicated load balancer - listener Shared load balancer - listener	1 minute
m2_act_conn	Active Connections	Number of TCP and UDP connections in the ESTABLISHED state between the monitored object and backend servers You can run the following command to view the connections (both Windows and Linux servers): netstat -an Unit: N/A	≥ 0
m3_inact_conn	Inactive Connections	Number of TCP connections between the monitored object and backend servers except those in the ESTABLISHED state You can run the following command to view the connections (both Windows and Linux servers): netstat -an Unit: N/A	≥ 0
m4_ncps	New Connections	Number of connections established between clients and the monitored object per second Unit: Count/s	≥ 0/second
m5_in_pps	Incoming Packets	Number of packets received by the monitored object per second Unit: Packet/s	≥ 0/second
m6_out_pps	Outgoing Packets	Number of packets sent from the monitored object per second Unit: Packet/s	≥ 0/second
m7_in_Bps	Inbound Rate	Traffic used for accessing the monitored object from the Internet per second Unit: byte/s	≥ 0 bytes/s
m8_out_Bps	Outbound Rate	Traffic used by the monitored object to access the Internet per second Unit: byte/s	≥ 0 bytes/s
m9_abnormal_servers	Unhealthy Servers	Number of unhealthy backend servers associated with the monitored object Unit: N/A	≥ 0	Dedicated load balancer Dedicated load balancer - listener Dedicated load balancer - backend server group	1 minute
ma_normal_servers	Healthy Servers	Number of healthy backend servers associated with the monitored object Unit: N/A	≥ 0		1 minute
m22_in_bandwidth	Inbound Bandwidth	Bandwidth used for accessing the monitored object from the Internet Unit: bit/s	≥ 0 bit/s	Dedicated load balancer Shared load balancer Dedicated load balancer - listener Shared load balancer - listener	1 minute
m23_out_bandwidth	Outbound Bandwidth	Bandwidth used by the monitored object to access the Internet Unit: bit/s	≥ 0 bit/s		1 minute
mb_l7_qps	Layer-7 Query Rate	Number of requests the monitored object receives per second Unit: Query/s	≥ 0 query/s	Dedicated load balancer Shared load balancer Dedicated load balancer - listener Shared load balancer - listener	1 minute
md_l7_http_3xx	Layer-7 3xx Status Codes	Number of 3xx status codes returned by the monitored object Unit: Count/s	≥ 0/second	Dedicated load balancer Shared load balancer Dedicated load balancer - listener Shared load balancer - listener	1 minute
mc_l7_http_2xx	Layer-7 2xx Status Codes	Number of 2xx status codes returned by the monitored object Unit: Count/s	≥ 0/second	Dedicated load balancer Shared load balancer Dedicated load balancer - listener Shared load balancer - listener	1 minute
me_l7_http_4xx	Layer-7 4xx Status Codes	Number of 4xx status codes returned by the monitored object Unit: Count/s	≥ 0/second
mf_l7_http_5xx	Layer-7 5xx Status Codes	Number of 5xx status codes returned by the monitored object Unit: Count/s	≥ 0/second
m10_l7_http_other_status	Layer-7 Other Status Codes	Number of status codes returned by the monitored object except 2xx, 3xx, 4xx, and 5xx status codes Unit: Count/s	≥ 0/second
m11_l7_http_404	Layer-7 404 Not Found	Number of 404 Not Found status codes returned by the monitored object Unit: Count/s	≥ 0/second
m12_l7_http_499	Layer-7 499 Client Closed Request	Number of 499 Client Closed Request status codes returned by the monitored object Unit: Count/s	≥ 0/second
m13_l7_http_502	Layer-7 502 Bad Gateway	Number of 502 Bad Gateway status codes returned by the monitored object Unit: Count/s	≥ 0/second
m14_l7_rt	Average Layer-7 Response Time	Average response time of the monitored object The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. Unit: ms NOTE: The average response time it takes to establish a WebSocket connection may be very high. This metric cannot be used as a reference.	≥ 0 ms
m15_l7_upstream_4xx	4xx Status Codes Backend	Number of 4xx status codes returned by the monitored object Unit: Count/s	≥ 0/second	Dedicated load balancer Shared load balancer Dedicated load balancer - listener Shared load balancer - listener Dedicated load balancer - backend server group	1 minute
m16_l7_upstream_5xx	5xx Status Codes Backend	Number of 5xx status codes returned by the monitored object Unit: Count/s	≥ 0/second
m17_l7_upstream_rt	Average Server Response Time	Average response time of backend servers The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. Unit: ms NOTE: The average response time it takes to establish a WebSocket connection may be very high. This metric cannot be used as a reference.	≥ 0 ms
m1a_l7_upstream_rt_max	Maximum Server Response Time	Maximum response time of backend servers (This metric is available only when the frontend protocol is HTTP or HTTPS.) The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. Unit: ms	≥ 0 ms	Dedicated load balancer Shared load balancer Dedicated load balancer - listener Shared load balancer - listener Dedicated load balancer - backend server group	1 minute
m1b_l7_upstream_rt_min	Minimum Server Response Time	Minimum response time of backend servers (This metric is available only when the frontend protocol is HTTP or HTTPS.) The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server. Unit: ms	≥ 0 ms		1 minute
m1c_l7_rt_max	Maximum Layer-7 Response Time	Maximum response time of the monitored object (This metric is available only when the frontend protocol is HTTP or HTTPS.) The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. Unit: ms	≥ 0 ms	Dedicated load balancer Shared load balancer Dedicated load balancer - listener Shared load balancer - listener	1 minute
m1d_l7_rt_min	Minimum Layer-7 Response Time	Minimum response time of the monitored object (This metric is available only when the frontend protocol is HTTP or HTTPS.) The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients. Unit: ms	≥ 0 ms		1 minute

a: If a service is being monitored from multiple dimensions, include all dimensions when you use APIs to query the metrics.

Example of querying a single metric from both dimensions: dim.0=lbaas_instance_id,223e9eed-2b02-4ed2-a126-7e806a6fee1f&dim.1=lbaas_listener_id,3baa7335-8886-4867-8481-7cbba967a917

Example of querying metrics in batches from both dimensions:

"dimensions": [
{
"name": "lbaas_instance_id",
"value": "223e9eed-2b02-4ed2-a126-7e806a6fee1f"
}
{
"name": "lbaas_listener_id",
"value": "3baa7335-8886-4867-8481-7cbba967a917"
}
],

Dimensions

Key	Value
lbaas_instance_id	ID of a dedicated load balancer ID of a shared load balancer
lbaas_listener_id	ID of a listener added to a dedicated load balancer ID of a listener added to a shared load balancer

Parent topic: Appendix

Предыдущая статья

Status Codes

Следующая статья

General Information About Enhanced Load Balancers

Была ли эта статья полезна?

Поддержка Юридические документы