Direct Connect
- Release Notes and Announcements
- Product Introduction
- Application Scenarios
- Operation Guide
- Connections
- Direct Connect Gateways
- CCN-based Direct Connect Gateways
- VPC-based Direct Connect Gateways
- Managing Direct Connect Gateways
- Dedicated Tunnels
- Monitoring and Alarming
- Cloud Exchange
- Practical Tutorial
- Cloud Access Management
- Practical Tutorial
- IDC Local Configuration
- BGP Routing Configuration Guide
- Establishing Direct Connect Between Tencent Cloud and Various Cloud Vendors Through Equinix
- API Documentation
- Making API Requests
- Direct Connect APIs
- Agreements
Alarm Overview
Last updated: 2025-04-22 16:47:28
Default Alarm Description
Default alarms are supported for the following events: DirectConnectDown, BandwidthRateOfDirectConnect, DirectConnectpacketerror, and DirectConnectTunnelRouteTableOverload. That is, after the above events occur, Tencent Cloud will actively trigger the alarm and promptly remind you to pay attention to business issues.
Note： Alarms may be triggered due to various reasons, some of which cannot be controlled on the cloud, such as business traffic surges, client device errors, intermediate cable disconnection, and malicious attacks. In this case, you can log in to Tencent Cloud and contact us for troubleshooting.
Metric | Default Alarm Description | Default Alarm Rule | Default Alarm Notification Channel |
BandwidthRateOfDirectConnect | The default alarm is triggered when the connection bandwidth utilization reaches 80% (current bandwidth value/connection bandwidth x 100%). | Statistical cycle: 1 minute. If the utilization reaches the threshold for 5 consecutive cycles, a default alarm notification is sent to the user. | SMS message (root account) and email |
Event Name | Event Description | Default Alarm Rule | Default Alarm Notification Channel |
DirectConnect Down | The connection is interrupted or abnormal. | Trigger an alarm when this event occurs and is fixed. | SMS message (root account) and email |
DirectConnect pkgerror | An inbound packet error occurs in the connection. | Statistical cycle: 1 minute. If the utilization reaches the threshold for 5 consecutive cycles, a default alarm notification is sent to the user. | SMS message (root account) and email |
DirectConnectTunnelRouteTableOverload | The number of dedicated tunnel BGP routes exceeds the limit. | Trigger an alarm when this event occurs and is fixed. | SMS message (root account) and email |
Metric Alarms
To create a metric alarm policy, you can configure the outbound bandwidth, inbound bandwidth, and bandwidth utilization as the trigger conditions for a connection; configure the outbound bandwidth and inbound bandwidth for a dedicated tunnel; and configure the outbound bandwidth, inbound bandwidth, outbound packet, and inbound packet for a direct connect gateway.
Metric | Description |
Outbound bandwidth | Average outbound traffic of the connection/dedicated tunnel/direct connect gateway per second. |
Inbound bandwidth | Average inbound traffic of the connection/dedicated tunnel/direct connect gateway per second |
Bandwidth utilization | Current bandwidth divided by connection bandwidth * 100%. |
Outbound packet | Average outbound packets of the direct connect gateway per second |
Inbound packet | Average inbound packets of the direct connect gateway per second. |
Event Alarms
You can use the
DirectConnectDown event as the trigger condition of event alarms for a dedication. You can use the DirectConnectTunnelDown, DirectConnectTunnelBGPSessionDown, DirectConnectTunnelRouteTableOverload, and DirectConnectTunnelBFDDown events as the trigger conditions of event alarms for a dedicated tunnel.Event Name | Event Parameter | Event Type | Dimension | Recoverable | Description | Troubleshooting Method |
Connection downtime | DirectConnectDown | Exception | Connection | Yes | The physical link of the connection is interrupted or has an exception | 1. Check whether the physical link has an exception or is interrupted (for example, the fiber cable is cut off, the line is unplugged, etc.). 2. Check whether the receiving port and optical/electrical modules are normal. 3. Check whether the network device port is closed. |
Dedicated tunnel downtime | DirectConnectTunnelDown | Exception | Dedicated tunnel | Yes | The physical link of the connection is interrupted or has an exception | 1. Check whether the physical link has an exception or is interrupted (for example, the fiber cable is cut off, the line is unplugged, etc.). 2. Check whether the receiving port and optical/electrical modules are normal. 3. Check whether the network device port is closed. |
Dedicated tunnel BGP session downtime | DirectConnectTunnelBGPSessionDown | Exception | Dedicated tunnel | Yes | The dedicated tunnel BGP session is interrupted | 1. Check whether the BGP process of the network device is normal. 2. Check whether the dedicated tunnel is normal. 3. Check whether the physical line is normal. |
Alarm for exceeded number of BGP tunnel routes | DirectConnectTunnelRouteTableOverload | Exception | Dedicated tunnel | No | The number of BGP session routes in a dedicated tunnel exceeds 80% of the threshold | Check whether routes published by the BGP session of the dedicated tunnel have reached 80% of the maximum, which is 100 by default. For more information, see Resource Limits. |
Dedicated tunnel BFD detection downtime | DirectConnectTunnelBFDDown | Exception | Dedicated tunnel | Yes | The dedicated tunnel BFD detection is interrupted | 1. Check whether the dedicated tunnel is normal. 2. Check whether the physical line is normal. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No