- Release Notes and Announcements
- Release Notes
- [September 9, 2024] Notification on Update of Compensation Standards in the Direct Connect Service Level Agreement
- [Oct. 2022] Discontinuing the Free Tier of Outbound Traffic and Introducing a New Pricing Plan
- Direct Connect Resource Lifecycle Standardization
- Dec. 31, 2022 - Migration of Direct Connect Cross-Region Tunnel Service to CCN
- Redundant Direct Connect Gateway Clearance
- Jun. 1, 2022 - Starts Commercialization of Shared Tunnel Service
- [Dec 1, 2020] Free Trial Period Extension and Billing Rule Change for Direct Connect Outbound Traffic
- Aug. 1, 2020 - Service Change Notice
- Dec. 31, 2021 - Direct Connect 2.0 Released
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Connections
- Direct Connect Gateways
- Dedicated Tunnels
- Monitoring and Alarming
- Cloud Exchange
- Cloud Access Management
- Practical Tutorial
- Connecting a Local IDC to CVM by Using a VPC NAT Gateway and Direct Connect
- Hybrid Cloud Primary/Secondary Communication (DC and VPN)
- Best Practices on Direct Connect High Availability and Hybrid Cloud Network
- Migrating Cross-Region Dedicated Tunnel to CCN
- Migrating IDC to the Cloud Through CCN
- Accelerating Routing Convergence Through BGP+BFD (Layer 3)
- IDC Local Configuration
- Establishing Direct Connect Between Tencent Cloud and Various Cloud Vendors Through Equinix
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Direct Connect APIs
- DescribeAccessPoints
- RejectDirectConnectTunnel
- ModifyDirectConnectTunnelAttribute
- DescribeDirectConnectTunnels
- DeleteDirectConnectTunnel
- CreateDirectConnectTunnel
- AcceptDirectConnectTunnel
- ModifyDirectConnectAttribute
- DescribeDirectConnects
- DeleteDirectConnect
- CreateDirectConnect
- ReleaseInternetAddress
- EnableInternetAddress
- DisableInternetAddress
- DescribeInternetAddressStatistics
- DescribeInternetAddressQuota
- DescribeInternetAddress
- ApplyInternetAddress
- Data Types
- Error Codes
- FAQ
- Troubleshooting
- Agreements
- Contact Us
- Glossary
- Release Notes and Announcements
- Release Notes
- [September 9, 2024] Notification on Update of Compensation Standards in the Direct Connect Service Level Agreement
- [Oct. 2022] Discontinuing the Free Tier of Outbound Traffic and Introducing a New Pricing Plan
- Direct Connect Resource Lifecycle Standardization
- Dec. 31, 2022 - Migration of Direct Connect Cross-Region Tunnel Service to CCN
- Redundant Direct Connect Gateway Clearance
- Jun. 1, 2022 - Starts Commercialization of Shared Tunnel Service
- [Dec 1, 2020] Free Trial Period Extension and Billing Rule Change for Direct Connect Outbound Traffic
- Aug. 1, 2020 - Service Change Notice
- Dec. 31, 2021 - Direct Connect 2.0 Released
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Connections
- Direct Connect Gateways
- Dedicated Tunnels
- Monitoring and Alarming
- Cloud Exchange
- Cloud Access Management
- Practical Tutorial
- Connecting a Local IDC to CVM by Using a VPC NAT Gateway and Direct Connect
- Hybrid Cloud Primary/Secondary Communication (DC and VPN)
- Best Practices on Direct Connect High Availability and Hybrid Cloud Network
- Migrating Cross-Region Dedicated Tunnel to CCN
- Migrating IDC to the Cloud Through CCN
- Accelerating Routing Convergence Through BGP+BFD (Layer 3)
- IDC Local Configuration
- Establishing Direct Connect Between Tencent Cloud and Various Cloud Vendors Through Equinix
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Direct Connect APIs
- DescribeAccessPoints
- RejectDirectConnectTunnel
- ModifyDirectConnectTunnelAttribute
- DescribeDirectConnectTunnels
- DeleteDirectConnectTunnel
- CreateDirectConnectTunnel
- AcceptDirectConnectTunnel
- ModifyDirectConnectAttribute
- DescribeDirectConnects
- DeleteDirectConnect
- CreateDirectConnect
- ReleaseInternetAddress
- EnableInternetAddress
- DisableInternetAddress
- DescribeInternetAddressStatistics
- DescribeInternetAddressQuota
- DescribeInternetAddress
- ApplyInternetAddress
- Data Types
- Error Codes
- FAQ
- Troubleshooting
- Agreements
- Contact Us
- Glossary
This document describes the metric alarms and event alarms for a connection, dedicated tunnel and direct connect gateway to help you configure alarm policies.
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. |
Yes
No
Was this page helpful?