You can use CM to set alarm rules for important metrics and events during data subscription. If a metric is exceptional or an event is triggered, CM will promptly send notifications to you, so you can take appropriate measures.
DTS supports default alarm configuration for some critical events, which means it will automatically monitor events when a task is started without having you to configure options and will notify you of triggered events. Currently, this feature is supported for the "data subscription task interruption" event.
Adding Alarm Policy
- Log in to the CM console.
- Click Alarm Configuration > Alarm Policy to enter the alarm policy configuration page.
- Click Add and configure a new alarm policy as shown below:
|Configuration Type||Configuration Item||Description|
||Policy Name||Custom policy name.|
|Remarks||Custom policy remarks.|
|Monitoring Type||Cloud product monitoring.|
||Select the desired policy type of the Tencent Cloud service to be monitored. Here, select DTS/Data subscription (Kafka Edition).
- Data migration: metrics and events in data migration scenarios are monitored.
- Data sync: metrics and events in data sync scenarios are monitored.
- Data subscription (Kafka Edition): metrics and events in data subscription (Kafka Edition) in new DTS are monitored.
- Data subscription: metrics and events in data subscription in old DTS are monitored.
- If you select **Instance ID**, the alarm policy will be associated with the selected instance.
- If you select **Instance Group**, the alarm policy will be associated with the selected instance group.
- If you select "All Objects", the alarm policy will be associated with all instances under the current account.
- Alarm trigger condition: you can choose to make the alarm triggered when any or all metrics meet the set condition.
- Configuration example: the metric is "binlog parsing delay", the statistical period is 1 minute, the comparison relation is ">", the threshold is "1", and the consecutive monitoring duration is "3 consecutive data points".
- Configuration effect: the "binlog parsing delay" metric is collected once every minute. If the difference between the GTIDs of the latest binlogs generated in the target and source databases is above 1 for three consecutive times, an alarm will be triggered.
- Alarm frequency: you can customize the frequency for repeated alarm notifications, such as once every hour, 2 hours, and 1 day.
|Configure manually (event alarm)
||Select the event to be monitored. The "data subscription task interruption" event has already been configured in the system by default.|
||Click *Select template** and select a configured template from the drop-down list. For detailed configurations, see Configuring Trigger Condition Template. If a newly created template is not displayed, click Refresh on the right.|
|Configure Alarm Notification
||You can select a preset or custom notification template. Each alarm policy can be bound to three notification templates at most.|
||After this option is enabled and configured successfully, an auto scaling policy will be triggered for scaling when the alarm condition is met.|
- After configuring the above information, click Save.
Modifying Alarm Policy
- Log in to the CM console.
- Click Alarm Configuration > Alarm Policy and click the name/ID of the policy to be modified to enter the alarm policy management page
- Modify information such as trigger condition, alarm object, and alarm notification.