Monitoring Metrics

Overview

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

Namespace

SYS.ELB

Metrics

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: Count	≥ 0	Shared load balancer, shared load balancer listener, or classic load balancer	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: Count	≥ 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: Count	≥ 0
m4_ncps	New Connections	Number of TCP and UDP connections established between clients and the monitored object per second Unit: Count	≥ 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 Unit: byte/s	≥ 0 bytes/s
m8_out_Bps	Outbound Rate	Traffic used by the monitored object to access the Internet Unit: byte/s	≥ 0 bytes/s
m9_abnormal_servers	Unhealthy Servers	Number of unhealthy backend servers associated with the monitored object Unit: Count	≥ 0	Shared load balancer or classic load balancer	1 minute
ma_normal_servers	Healthy Servers	Number of healthy backend servers associated with the monitored object Unit: Count	≥ 0	Shared load balancer or classic load balancer	1 minute

a: If a service has multiple dimensions, you must specify 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
lb_instance_id	Specifies the ID of the classic load balancer.
lbaas_instance_id	Specifies the ID of the shared load balancer.
lbaas_listener_id	Specifies the ID of the shared load balancer listener.