- Release Notes and Announcements
- Release Notes
- 400G Ports Supported for Direct Connect
- [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
- 400G Ports Supported for Direct Connect
- [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
You can configure alarm rules for the connection, dedicated tunnel and direct connect gateway on the Cloud Monitor console. When an alarm rule is triggered, you will receive notifications via the channel you specified, helping you take appropriate measures.
Directions
1. Log in to the Cloud Monitor console and choose Alarm Configuration > Alarm Policy on the left sidebar.
2. Click Create on the Alarm Policy page.
3. Configure a new alarm policy as instructed below.
4. Edit Policy name and Remarks. Select Connection, Dedicated tunnel or Direct connect gateway for Policy type as needed.
Note:
If Direct connect gateway is selected, the policy is VPC-based.
5. Choose a project to which the alarm policy belongs. Each project supports creating a maximum of 300 alarm policies.
6. Select the alarm object.
If you select All objects, the alarm policy will be associated with all instances under the current account.
If you select Instance ID and select instances in the pop-up window, the alarm policy will be associated with the selected instances.
If you select Instance group, the alarm policy will be associated with the selected instance group. If there is no available instance group, you can click Create instance group to configure one.
7. Configure the trigger condition using either of:
Template
Click Select template and select a configured template in the drop-down list.
Note:
You can click Add trigger condition template to configure a new trigger condition template. For more information about the configurations, please see Configuring Trigger Condition Template. If the new template is not displayed in the list, click Refresh.
Manual configuration
Set the trigger condition as needed after selecting Manual configuration. You can click Add metric to configure a new metric. For more information about metric alarms, see Alarm Overview.
For example, if you choose Inbound bandwidth metric and configure as follows: statistical period: 1 minute, >, 100 Mbps, at 2 consecutive data points, and Alarm once a day, then the inbound bandwidth data will be collected once every minute. An alarm will be triggered once a day if the inbound bandwidth of a connection, dedicated tunnel or direct connect gateway exceeds 100 Mbps for two consecutive minutes.
Note:
Click Add metric to configure a new trigger condition. You can choose to trigger an alarm when any or all conditions are met.
If you need to configure event alarms, see Quickly Configuring Cloud Monitor Event Alarm Push.
8. Configure alarm notification.
The notification template allows you to configure alarm recipients. You can click Select template and select an existing template, or click Create template to configure a new template as prompted.
9. (Optional) Configure the API callback.
i. Click Create template. In the pop-up window, click For more configurations, please go to notification template page.
ii. On the New notification template page, complete the notification template configurations, enter a URL accessible over public networks as the API callback address (domain name or IP[:port][/path]), and click Complete.
iii. Go to the Alarm policy page and select the alarm notification template you’ve just created.
Then Cloud Monitor will push the alarm information to this address in time.
10. Click OK.
Managing Alarm Policies
Once an alarm policy is created, you can enable, disable, copy, or delete it on the console.
1. Log in to the Cloud Monitor console and select Alarm Configuration > Alarm Policy on the left sidebar to access the Alarm policy page.
2. Perform the following steps as needed.
To enable or disable an alarm policy, toggle the switch in its Alarm On-Off column.
To copy an alarm policy, click Copy in its Operation column, modify the policy as needed in the pop-up window, and click Complete.
To view historical alarm data, locate the alarm policy and click Alarm records in the Operation column.
To delete an alarm policy, click Delete in its Operation column, and click Confirm in the pop-up dialog box.
Yes
No
Was this page helpful?