Supported Metrics
Function
This section describes monitoring metrics reported by Enterprise Router to Cloud Eye as well as their namespaces, metrics, and dimensions. You can use the Cloud Eye management console or APIs to obtain the monitoring metrics and alarms generated for Enterprise Router.
Namespace
SYS.ER
Metrics
ID |
Name |
Description |
Value Range |
Unit |
Conversion Rule |
Monitored Object (Dimension) |
Monitoring Interval (Raw Data) |
---|---|---|---|---|---|---|---|
instance_bytes_in |
Inbound Traffic |
Network traffic going into the enterprise router |
≥ 0 |
Byte |
1024 (IEC) |
Enterprise router |
1 minute |
instance_bytes_out |
Outbound Traffic |
Network traffic going out of the enterprise router |
≥ 0 |
Byte |
1024 (IEC) |
Enterprise router |
1 minute |
instance_bits_rate_in |
Inbound Bandwidth |
Network traffic per second going into the enterprise router |
≥ 0 |
bit/s |
1000 (SI) |
Enterprise router |
1 minute |
instance_bits_rate_out |
Outbound Bandwidth |
Network traffic per second going out of the enterprise router |
≥ 0 |
bit/s |
1000 (SI) |
Enterprise router |
1 minute |
instance_packets_in |
Inbound PPS |
Packets per second going into the enterprise router |
≥ 0 |
PPS |
1000 (SI) |
Enterprise router |
1 minute |
instance_packets_out |
Outbound PPS |
Packets per second going out of the enterprise router |
≥ 0 |
PPS |
1000 (SI) |
Enterprise router |
1 minute |
instance_packets_drop_blackhole |
Packets Dropped by Black Hole Route |
The number of packets dropped because they matched a black hole route on the enterprise router |
≥ 0 |
Count |
N/A |
Enterprise router |
1 minute |
instance_packets_drop_noroute |
Packets Dropped Due to No Matching Routes |
The number of packets dropped because they did not match a route on the enterprise router |
≥ 0 |
Count |
N/A |
Enterprise router |
1 minute |
ID |
Name |
Description |
Value Range |
Unit |
Conversion Rule |
Monitored Object (Dimension) |
Monitoring Interval (Raw Data) |
---|---|---|---|---|---|---|---|
attachment_bytes_in |
Inbound Traffic |
Network traffic going into the attachment |
≥ 0 |
Byte |
1024 (IEC) |
Attachment |
1 minute |
attachment_bytes_out |
Outbound Traffic |
Network traffic going out of the attachment |
≥ 0 |
Byte |
1024 (IEC) |
Attachment |
1 minute |
attachment_bits_rate_in |
Inbound Bandwidth |
Network traffic per second going into the attachment |
≥ 0 |
bit/s |
1000 (SI) |
Attachment |
1 minute |
attachment_bits_rate_out |
Outbound Bandwidth |
Network traffic per second going out of the attachment |
≥ 0 |
bit/s |
1000 (SI) |
Attachment |
1 minute |
attachment_packets_in |
Inbound PPS |
Packets per second going into the attachment |
≥ 0 |
PPS |
1000 (SI) |
Attachment |
1 minute |
attachment_packets_out |
Outbound PPS |
Packets per second going out of the attachment |
≥ 0 |
PPS |
1000 (SI) |
Attachment |
1 minute |
attachment_packets_drop_blackhole |
Packets Dropped by Black Hole Route |
The number of packets dropped because they matched a black hole route on the attachment |
≥ 0 |
Count |
N/A |
Attachment |
1 minute |
attachment_packets_drop_noroute |
Packets Dropped Due to No Matching Routes |
The number of packets dropped because they did not match a route on the attachment |
≥ 0 |
Count |
N/A |
Attachment |
1 minute |
- Query a single metric:
dim.0=er_instance_id,d9f7b61f-e211-4bce-ac5f-2b76f3d0cf1d&dim.1=er_attachment_id,659614a0-e559-46c0-86ca-00c03c3d61b8
- Query metrics in batches:
"dimensions": [ { "name": "er_instance_id", "value": "d9f7b61f-e211-4bce-ac5f-2b76f3d0cf1d" }, { "name": "er_attachment_id", "value": "659614a0-e559-46c0-86ca-00c03c3d61b8" } ]
Dimensions
Key |
Value |
---|---|
er_instance_id |
Enterprise router |
er_attachment_id |
Attachment |
- The monitoring metric measurement dimension of an enterprise router is er_instance_id.
- The monitoring metric measurement dimensions of an attachment are er_instance_id and er_attachment_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