Monitoring Metrics
Overview
This section describes the metrics that can be monitored by Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye to query the metrics of a monitored object and the generated alarms.
Namespace
SYS.ELB
Metrics
Metric ID |
Name |
Description |
Value |
Monitored Object |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
m1_cps |
Concurrent Connections |
Number of TCP and UDP connections between the monitored object and backend servers Unit: Count |
≥ 1 |
Load balancer or 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: Count |
≥ 1 |
||
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 |
≥ 1 |
||
m4_ncps |
New Connections |
Number of TCP and UDP connections established between clients and the monitored object per second Unit: Count |
≥ 1/s |
||
m5_in_pps |
Incoming Packets |
Number of packets received by the monitored object per second Unit: Packet/s |
≥ 1/s |
||
m6_out_pps |
Outgoing Packets |
Number of packets sent from the monitored object per second Unit: Packet/s |
≥ 1/s |
||
m7_in_Bps |
Inbound Rate |
Traffic used for accessing the monitored object from the Internet Unit: byte/s |
≥ 1 byte/s |
||
m8_out_Bps |
Outbound Rate |
Traffic used by the monitored object to access the Internet Unit: byte/s |
≥ 1 byte/s |
||
m9_abnormal_servers |
Unhealthy Servers |
Number of unhealthy backend servers associated with the monitored object Unit: Count |
≥ 1 |
Load balancer |
1 minute |
ma_normal_servers |
Healthy Servers |
Number of healthy backend servers associated with the monitored object Unit: Count |
≥ 1 |
||
Layer 7 (HTTP/HTTPS) metrics |
|||||
mb_l7_qps |
Layer-7 Query Rate |
Number of requests the monitored object receives per second (This metric is available only when the frontend protocol is HTTP or HTTPS.) Unit: Query/s |
≥ 1/s |
Load balancer or listener |
1 minute |
mc_l7_http_2xx |
2xx Status Codes |
Number of 2xx status codes returned by the monitored object (This metric is available only when the frontend protocol is HTTP or HTTPS.) Unit: Count/s |
≥ 1/s |
||
md_l7_http_3xx |
3xx Status Codes |
Number of 3xx status codes returned by the monitored object (This metric is available only when the frontend protocol is HTTP or HTTPS.) Unit: Count/s |
≥ 1/s |
||
me_l7_http_4xx |
4xx Status Codes |
Number of 4xx status codes returned by the monitored object (This metric is available only when the frontend protocol is HTTP or HTTPS.) Unit: Count/s |
≥ 1/s |
||
mf_l7_http_5xx |
5xx Status Codes |
Number of 5xx status codes returned by the monitored object (This metric is available only when the frontend protocol is HTTP or HTTPS.) Unit: Count/s |
≥ 1/s |
||
m10_l7_http_other_status |
Other Status Codes |
Number of status codes returned by the monitored object except 2xx, 3xx, 4xx, and 5xx status codes (This metric is available only when the frontend protocol is HTTP or HTTPS.) Unit: Count/s |
≥ 1/s |
||
m11_l7_http_404 |
404 Not Found |
Number of 404 Not Found status codes returned by the monitored object (This metric is available only when the frontend protocol is HTTP or HTTPS.) Unit: Count/s |
≥ 1/s |
||
m12_l7_http_499 |
499 Client Closed Request |
Number of 499 Client Closed Request status codes returned by the monitored object (This metric is available only when the frontend protocol is HTTP or HTTPS.) Unit: Count/s |
≥ 1/s |
||
m13_l7_http_502 |
502 Bad Gateway |
Number of 502 Bad Gateway status codes returned by the monitored object (This metric is available only when the frontend protocol is HTTP or HTTPS.) Unit: Count/s |
≥ 1/s |
||
m14_l7_rt |
Average Layer-7 Response Time |
Average 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 |
≥ 1 ms |
a: If a service has multiple dimensions, all dimensions are mandatory 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" } ],
Dimension
Key |
Value |
---|---|
lbaas_instance_id |
Specifies the load balancer ID. |
lbaas_listener_id |
Specifies the listener ID. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot