Monitoring Metrics
Overview
This section describes the namespace, list, and measurement dimensions of metrics of EIPs and bandwidths that you can check on Cloud Eye. You can use APIs or the Cloud Eye console to query the metrics of the monitored metrics and generated alarms.
 
 
    - Cloud Eye can monitor dimensions nested to a maximum depth of four levels (levels 0 to 3). 3 is the deepest level. For example, if the dimension information of a monitoring metric is "bandwidth_id,publicip_id", the dimension of "bandwidth_id" is numbered 0 and that of "publicip_id" is 1.
- If a bandwidth is increased or decreased, there is a delay of 5 to 10 minutes for the monitoring metrics to update for the new bandwidth.
Namespace
Namespace of EIPs and bandwidths: SYS.VPC
Monitoring Metrics
| ID | Name | Description | Value Range | Unit | Conversion Rule | Monitored Object (Dimension) | Monitoring Interval (Raw Data) | 
|---|---|---|---|---|---|---|---|
| upstream_bandwidth | Outbound Bandwidth | Network rate of outbound traffic (Previously called "Upstream Bandwidth") | ≥ 0 | bit/s | 1000 (SI) | bandwidth_id,publicip_id | 1 minute | 
| downstream_bandwidth | Inbound Bandwidth | Network rate of inbound traffic (Previously called "Downstream Bandwidth") | ≥ 0 | bit/s | 1000 (SI) | bandwidth_id,publicip_id | 1 minute | 
| upstream_bandwidth_usage | Outbound Bandwidth Usage | Usage of outbound bandwidth in the unit of percent. Outbound bandwidth usage = Outbound bandwidth/Purchased bandwidth | 0-100 | % | N/A | bandwidth_id,publicip_id | 1 minute | 
| downstream_bandwidth_usage | Inbound Bandwidth Usage | Usage of inbound bandwidth in the unit of percent. Inbound bandwidth usage = Inbound bandwidth/Purchased bandwidth | 0-100 | % | N/A | bandwidth_id,publicip_id | 1 minute | 
| up_stream | Outbound Traffic | Network traffic going out of the cloud platform (Previously called "Upstream Traffic") | ≥ 0 | Byte | 1000 (SI) | bandwidth_id,publicip_id | 1 minute | 
| down_stream | Inbound Traffic | Network traffic going into the cloud platform (Previously called "Downstream Traffic") | ≥ 0 | Byte | 1000 (SI) | bandwidth_id,publicip_id | 1 minute | 
If an object is in a hierarchical system, specify the monitored dimension in hierarchical form when you use an API to query the metrics of this object.
For example, to query the outbound traffic (up_stream) of an EIP, the dimension of the metric is bandwidth_id,publicip_id, where bandwidth_id indicates level 0 and publicip_id indicates level 1.
- To query a single metric by calling an API, the mount_point dimension is used as follows: 
     dim.0=bandwidth_id,530cd6b0-86d7-4818-837f-935f6a27414d&dim.1=publicip_id,3773b058-5b4f-4366-9035-9bbd9964714a 530cd6b0-86d7-4818-837f-935f6a27414d and 3773b058-5b4f-4366-9035-9bbd9964714a are the dimension values of bandwidth_id and publicip_id, respectively. For details about how to obtain the values, see Dimensions. 
- To query multiple metrics by calling an API, the mount_point dimension is used as follows: 
     "dimensions": [ { "name": "bandwidth_id", "value": "530cd6b0-86d7-4818-837f-935f6a27414d" } { "name": "publicip_id", "value": "3773b058-5b4f-4366-9035-9bbd9964714a" } ]530cd6b0-86d7-4818-837f-935f6a27414d and 3773b058-5b4f-4366-9035-9bbd9964714a are the dimension values of bandwidth_id and publicip_id, respectively. For details about how to obtain the values, see Dimensions. 
Dimensions
| Key | Value | 
|---|---|
| publicip_id | EIP ID You can call the API Querying an EIP to obtain the value from the response parameters. | 
| bandwidth_id | Bandwidth ID You can call the API Querying a Bandwidth to obtain the value from the response parameters. | 
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 
    