Help Docs

How to monitor the Enterprise Router (ER) in Huawei Cloud

Site24x7 continuously monitors your Enterprise Router (ER) metrics, giving your team real-time visibility into instance-level traffic throughput, packet delivery rates, and drop events across both router instances and individual attachments.

Use cases

Routing resilience: Spikes in Drops indicate that traffic is being discarded due to missing or misconfigured routes. Alerting on these counters helps your team resolve routing gaps before entire application segments lose connectivity.

Attachment-level visibility: Tracking Attachment Traffic lets your team pinpoint which VPC, VPN, or direct link is overloaded. Rebalancing or resizing attachments helps prevent the router from becoming a bottleneck.

Capacity assurance: Inbound and Outbound Bit Rates give a continuous view of router utilization against provisioned capacity. Setting thresholds helps trigger proactive scaling before throughput limits degrade inter-VPC latency.

Setup and configuration

Enterprise Router resources are auto-discovered and monitored during the Huawei Cloud integration. To enable monitoring, follow the steps below:

  1. Navigate to Cloud > Huawei > Add Huawei Monitor. Follow these steps to add a Huawei Cloud monitor.
  2. While adding or editing a Huawei Cloud monitor, select ER from the Service/Resource Types drop-down and click Save.
  3. Navigate to Cloud > Huawei, select the created Huawei monitor, and then click Enterprise Router.

Supported metrics

Traffic

Metric name

Description

Units

Instance Inbound Bytes Total bytes received by the Enterprise Router (ER) instance across all attachments in the monitoring period. Byte
Instance Outbound Bytes Total bytes transmitted by the ER instance across all attachments in the monitoring period. Byte
Attachment Inbound Bytes Total bytes received through a specific attachment connected to the ER. Byte
Attachment Outbound Bytes Total bytes transmitted through a specific attachment connected to the ER. Byte

Network

Metric name

Description

Units

Instance Inbound Bits Rate Rate of bits received by the ER instance per second, reflecting overall ingress throughput. Bit/second
Instance Outbound Bits Rate Rate of bits transmitted by the ER instance per second, reflecting overall egress throughput. Bit/second
Instance Inbound Packets Total number of packets received by the ER instance in the monitoring period. Count
Instance Outbound Packets Total number of packets transmitted by the ER instance in the monitoring period. Count
Attachment Inbound Bits Rate Rate of bits received through a specific attachment per second. Bit/second
Attachment Outbound Bits Rate Rate of bits transmitted through a specific attachment per second. Bit/second
Attachment Inbound Packets Total packets received through a specific attachment in the monitoring period. Packet/second
Attachment Outbound Packets Total packets transmitted through a specific attachment in the monitoring period. Packet/second

Drops

Metric name

Description

Units

Instance Blackhole Dropped Packets Number of packets dropped at the instance level because they matched a blackhole route entry. Count
Instance No-Route Dropped Packets Number of packets dropped at the instance level because no matching route was found in the routing table. Count

Attachment Traffic

Metric name

Description

Units

Attachment Inbound Bytes Total bytes received through a specific attachment in the monitoring interval, providing per-attachment ingress volume. Byte
Attachment Outbound Bytes Total bytes transmitted through a specific attachment in the monitoring interval, providing per-attachment egress volume. Byte

Attachment Network

Metric name

Description

Units

Attachment Inbound Bits Rate Rate of bits per second received through a specific attachment, reflecting real-time ingress load on that connection. Bit/second
Attachment Outbound Bits Rate Rate of bits per second transmitted through a specific attachment, reflecting real-time egress load on that connection. Bit/second
Attachment Inbound Packets Total packets received through a specific attachment, useful for comparing packet counts against byte volumes. Count
Attachment Outbound Packets Total packets transmitted through a specific attachment in the monitoring period. Count

Attachment Drops

Metric name

Description

Units

Attachment Blackhole Dropped Packets Number of packets dropped on a specific attachment because they matched a blackhole route. Count
Attachment No-Route Dropped Packets Number of packets dropped on a specific attachment because no route was available to forward them. Count

Dependency View

The Dependency View tab maps GeminiDB Cassandra groups based on your customer requirements. Contact support and share your requirements to help us prioritize dependency mapping for the GaussDB Cassandra groups in your account.

Common monitored data

Outages

The Outages tab displays outage details, including start time, end time, duration, and related comments, to help track and review downtime events.

Notes

The Notes tab enables you to record descriptions, operational context, runbook steps, recent changes, and reference links to keep your team informed. Format the content using markdown syntax.

Log Report

The Log Report tab provides a unified view of the respective monitor's log status and supports CSV downloads for analysis and auditing.  

Alert Logs

The Alert Logs tab provides a comprehensive list of all alerts generated by the monitor. Easily track key details such as the monitored resource name, alert trigger time, root cause, and notification status. Learn more.

Threshold configuration

You can configure thresholds and alerts for all ER metrics to proactively detect performance degradation and connection issues.

Go to Admin > Configuration Profiles > Threshold and Availability to create or modify your alert profiles.

IT Automation

Use Site24x7's IT Automation to resolve common issues with ER performance automatically:

  1. Go to Admin > IT Automation Templates. Then, click Add Automation Templates.
  2. Create an automation rule by selecting the automation Type (e.g., Server reboot, clear queue).
  3. Map the created rules to the ER monitor for automatic execution during alerts.

Configuration rules

Use Configuration Rules to simplify bulk setup across ER instances. Automatically assign Threshold Profiles, Notification Profiles, Tags, and Monitor Groups when new monitors are discovered.

Related articles

Was this document helpful?

Would you like to help us improve our documents? Tell us what you think we could do better.


We're sorry to hear that you're not satisfied with the document. We'd love to learn what we could do to improve the experience.


Thanks for taking the time to share your feedback. We'll use your feedback to improve our online help resources.

Shortlink has been copied!