- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Permissions Management
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
-
Routing Control
-
Route Policies
- Route Policy Overview
- Creating a Route Policy
- Associating a Route Policy with an Enterprise Router
- Changing the Route Policy Associated with an Enterprise Router
- Disassociating a Route Policy from an Enterprise Router
- Modifying a Route Policy
- Viewing a Route Policy
- Deleting a Route Policy
- Adding a Policy Node to a Route Policy
- Modifying a Policy Node in a Route Policy
- Exporting Policy Nodes in a Route Policy
- Viewing a Policy Node in a Route Policy
- Deleting a Policy Node from a Route Policy
-
IP Prefix Lists
- IP Prefix List Overview
- Creating an IP Prefix List
- Modifying the Name of an IP Prefix List
- Viewing an IP Prefix List
- Deleting an IP Prefix List
- Adding a Prefix Rule to an IP Address Prefix List
- Modifying an IP Prefix Rule in an IP Prefix List
- Exporting Prefix Rules in an IP Prefix List
- Viewing a Prefix Rule in an IP Prefix List
- Deleting a Prefix Rule from an IP Prefix List
-
AS_Path Lists
- AS_Path List Overview
- Creating an AS_Path List
- Modifying the Name of an AS_Path List
- Viewing an AS_Path List
- Deleting an AS_Path List
- Adding an AS_Path Filter to an AS_Path List
- Exporting AS_Path Filters in an AS_Path List
- Viewing an AS_Path Filter in an AS_Path List
- Deleting an AS_Path Filter from an AS_Path List
-
Route Policies
- Sharing
- Flow Logs
- Monitoring and Auditing
- Tags
- Quotas
-
Best Practices
- Summary on Enterprise Router Best Practices
- Connecting VPCs Across Regions Using Enterprise Router and Central Network
- Using Enterprise Router to Isolate VPCs in the Same Region
- Using a Third-Party Firewall to Protect VPCs Connected by Enterprise Routers
- Enabling an On-Premises Data Center to Access Service VPCs Using an Enterprise Router and Transit VPC
- Setting Up a Hybrid Cloud Network Using Enterprise Router and Direct Connect Global DC Gateway
-
Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
- Overview
- Network and Resource Planning
- Process of Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
- Procedure for Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
-
Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Overview
- Network and Resource Planning
- Process of Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Procedure for Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router, VPN, and Direct Connect (Global DC Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router and Direct Connect (Virtual Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Virtual Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router, VPN, and Direct Connect (Virtual Gateway)
- Allowing VPCs to Share an EIP to Access the Internet Using Enterprise Router and NAT Gateway
- Using Enterprise Router to Migrate the Network Set Up Through VPC Peering
- Using Enterprise Router to Migrate the Network Set Up Through Direct Connect (Global DC Gateway)
- Using Enterprise Router and Central Network to Migrate the Network Set Up Through a Cloud Connection
- API Reference
- FAQs
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
- Sharing
- Flow Logs
- Monitoring
- Interconnecting with CTS
- Permissions Management
- Tags
- Quotas
- FAQ
- Change History
-
User Guide (Ankara Region)
- Service Overview
- Getting Started
- Permissions Management
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
- Sharing
- Flow Logs
- Monitoring
- Quotas
- FAQ
- Change History
- API Reference (Ankara Region)
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Show all
Copied.
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 |
Monitored Object |
Monitoring Interval (Raw Data) |
---|---|---|---|---|---|
instance_bytes_in |
Inbound Traffic |
Network traffic going into the enterprise router Unit: byte |
≥ 0 |
Enterprise router |
1 minute |
instance_bytes_out |
Outbound Traffic |
Network traffic going out of the enterprise router Unit: byte |
≥ 0 |
Enterprise router |
1 minute |
instance_bits_rate_in |
Inbound Bandwidth |
Network traffic per second going into the enterprise router Unit: bit/s |
≥ 0 |
Enterprise router |
1 minute |
instance_bits_rate_out |
Outbound Bandwidth |
Network traffic per second going out of the enterprise router Unit: bit/s |
≥ 0 |
Enterprise router |
1 minute |
instance_packets_in |
Inbound PPS |
Packets per second going into the enterprise router Unit: packet/s |
≥ 0 |
Enterprise router |
1 minute |
instance_packets_out |
Outbound PPS |
Packets per second going out of the enterprise router Unit: packet/s |
≥ 0 |
Enterprise router |
1 minute |
instance_packets_drop_blackhole |
Packets Dropped by Black Hole Route |
Packets dropped by black hole route of the enterprise router Unit: count |
≥ 0 |
Enterprise router |
1 minute |
instance_packets_drop_noroute |
Packets Dropped Due to No Matching Routes |
Packets dropped because the enterprise router has no matching routes Unit: count |
≥ 0 |
Enterprise router |
1 minute |
ID |
Name |
Description |
Value Range |
Monitored Object |
Monitoring Interval (Raw Data) |
---|---|---|---|---|---|
attachment_bytes_in |
Inbound Traffic |
Network traffic going into the attachment Unit: byte |
≥ 0 |
Attachment |
1 minute |
attachment_bytes_out |
Outbound Traffic |
Network traffic going out of the attachment Unit: byte |
≥ 0 |
Attachment |
1 minute |
attachment_bits_rate_in |
Inbound Bandwidth |
Network traffic per second going into the attachment Unit: bit/s |
≥ 0 |
Attachment |
1 minute |
attachment_bits_rate_out |
Outbound Bandwidth |
Network traffic per second going out of the attachment Unit: bit/s |
≥ 0 |
Attachment |
1 minute |
attachment_packets_in |
Inbound PPS |
Packets per second going into the attachment Unit: packet/s |
≥ 0 |
Attachment |
1 minute |
attachment_packets_out |
Outbound PPS |
Packets per second going out of the attachment Unit: packet/s |
≥ 0 |
Attachment |
1 minute |
attachment_packets_drop_blackhole |
Packets Dropped by Black Hole Route |
Packets dropped by black hole route of the attachment Unit: count |
≥ 0 |
Attachment |
1 minute |
attachment_packets_drop_noroute |
Packets Dropped Due to No Matching Routes |
Packets dropped because the attachment has no matching routes Unit: count |
≥ 0 |
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