Data Transmission Service (DTS) is integrated with CloudMonitor. You can use the event subscription feature of CloudMonitor to configure custom alert notifications for important events. This lets you be promptly notified of event occurrences and progress, which helps you quickly analyze and troubleshoot issues during business exceptions.
Background information
CloudMonitor is a service that monitors Internet applications and Alibaba Cloud resources. You can configure CloudMonitor to notify you of system anomalies. Then, you can automate the anomaly handling process based on alert notifications. CloudMonitor supports the following alert notification methods:
Sends alert notifications to you by using emails, text messages, or DingTalk chatbots.
Push events to Simple Message Queue (formerly MNS), Function Compute, Simple Log Service, or the specified callback URL. This allows you to automate the anomaly handling process based on your business requirements.
Prerequisites
ApsaraDB Fault or Maintenance Notifications is enabled and a contact is specified in the Message Center console. We recommend that you specify an O&M engineer as the contact.
Create alert contacts and alert contact groups. Then, add the alert contacts to the alert contact groups. For more information, see Create an alert contact or an alert contact group.
Create a subscription policy
Log on to the CloudMonitor console.
In the navigation pane on the left, choose .
NoteIf the Event Subscription page is not displayed, see Set alert rules for DTS tasks in the CloudMonitor console.
On the Subscription Policy tab, click Create Subscription Policy.
On the Create Subscription Policy page, set the parameters for the subscription policy.
If you set Subscription Type to System Event, set Product to Data Transmission in the Subscription Scope section.
NoteFor information about the system events that DTS supports, see System events.
If you set Subscription Type to Threshold Event, search for Data Transmission Service in the Product Classification section and select an option as needed.
Configure other parameters as needed. For more information, see Subscription policy parameters.
After you complete the configuration, click Submit.
To view, modify, or delete subscribed CloudMonitor events, see Manage event subscriptions (Recommended).
Debug an event subscription
Log on to the CloudMonitor console.
In the navigation pane on the left, choose .
NoteIf the Event Subscription page is not displayed, see Set alert rules for DTS tasks in the CloudMonitor console.
On the Event Subscription page, click the Debug Event Subscription tab.
In the Create Event Debugging panel, configure the debug event.
Set Product to Data Transmission.
Select a Name as needed.
NoteName is the NameDesc parameter of the system event.
You cannot debug the Task Relocation Due To Underlying Hardware Upgrade series or the Instance Task Latency events.
The system automatically generates the debug content in JSON format.
Modify the debug content as needed.
For an example of how to modify the content, see Event content examples.
Click OK.
The Operation successful message appears. CloudMonitor automatically sends a test alert notification to the alert contacts based on the notification methods specified in the subscription policy.
Event content examples
Synchronization, migration, and tracking tasks
Parameter description
Parameter | Description | Example value |
product | The cloud product to which the system event belongs (Product). |
|
resourceId | The affected resource. Note The value starts with |
|
level | The level of the system event (Level).
|
|
instanceName | The name of the affected instance. Format: |
|
regionId | The region of the instance. |
|
name | The name of the system event (Name). |
|
content | The content of the system event. |
|
msg | ||
status | The status of the system event (Status).
|
|
Examples
Name | Content example |
Synchronization Task Abnormal | |
Synchronization Task Recovered | |
Migration Task Abnormal | |
Migration Task Recovered | |
Tracking Task Abnormal | |
Tracking Task Recovered | |
Instance tasks
Parameter description
Parameter | Description | Example value |
product | The cloud product to which the system event belongs (Product). |
|
resourceId | The affected resource. Note The value starts with |
|
level | The level of the system event (Level). Note The level for instance task exceptions is always WARN (warning). |
|
instanceName | The name of the affected instance. Format: |
|
regionId | The region of the instance. |
|
name | The name of the system event (Name). |
|
content | The content of the system event. |
|
eventId | The ID of the system event. |
|
publishTime | The time when the system event was published. The time is in UTC. |
|
reason | The reason why the system event was triggered. |
|
product | The cloud product to which the event belongs. |
|
instanceComment | The ID of the affected instance. |
|
instanceId | ||
extra | The extra information about the content of the system event. |
|
eventTime | The start time of the system event. The time is in UTC. |
|
cloudEvent | The information about the CloudMonitor event. |
|
data | The data overview of the system event. |
|
gmtModified | The update time. The time is in UTC. |
|
eventCategory | The categorization of the event (EventType). Note The categorization for instance task exceptions is always Exception. |
|
gmtCreated | The time when the event was created. The time is in UTC. |
|
detailReason | The detailed reason why the event was triggered. |
|
uid | The Alibaba Cloud account ID. |
|
cmsProduct | The cloud product to which the event belongs. |
|
instanceId | The ID of the affected instance. |
|
eventLevel | The level of the event (Level). Note The level for instance task exceptions is always WARN (warning). |
|
handleStatus | The processing status of the event. |
|
startTime | The start time of the event. The time is in UTC. |
|
detailImpact | The pagination parameter. |
|
eventId | The ID of the event. |
|
product | The cloud product to which the event belongs. |
|
dbType | ||
hasLifeCycle | Indicates whether the event has a lifecycle.
|
|
eventType | The type of the event. |
|
eventReason | The source of the event. |
|
eventImpact | The impact of the event. |
|
mainEventId | The ID of the main event. |
|
eventCode | The code of the event, which is the value of Name. |
|
isClosed | Indicates whether the event is closed.
|
|
regionId | The region of the instance. |
|
sourceType | The type of the source data. |
|
eventStatus | The status of the system event (Status).
|
|
endTime | The end time of the event. |
|
eventDetail | The details of the event. The details include the task type (dts_task_type), task ID (dts_job_id), task status (job_state), error code (err_code), and detailed information about the task exception (err_msg_detail and message). |
|
resourceType | The resource type.
|
|
subject | The affected resource. Note The value starts with |
|
specversion | The CloudEvents protocol version. |
|
time | The time when the event was created. The time is in UTC. |
|
source | The source of the event. |
|
id | The ID of the event. |
|
region | The region of the instance. |
|
type | The type of the event. |
|
region | The region of the instance. |
|
instanceType | The resource type.
|
|
eventType | The categorization of the event. |
|
status | The status of the system event (Status).
|
|
Examples
Name | Content example |
Instance Task Exception Recovered | |
Instance Task Exception Started | |
Task relocation due to underlying hardware upgrade
Parameter description
Parameter | Description | Example value |
product | The cloud product to which the system event belongs (Product). |
|
userId | The Alibaba Cloud account ID. |
|
level | The level of the system event (Level).
|
|
resourceId | The affected resource. Note The value starts with |
|
instanceName | The name of the affected instance. Format: |
|
dryRun | Indicates whether to perform only a preflight request.
|
|
ver | The CloudEvents protocol version. |
|
trace | The request ID. |
|
name | The name of the system event (Name). |
|
regionId | The region of the instance. |
|
status | The status of the system event (Status).
|
|
time | The time when the system event was generated. |
|
content | The content of the system event. Note The content can include information such as the task or instance name (jobName), the estimated running time of the system event (innerScheduleTime), the instance ID (instanceId), and the instance region (region). |
|
Examples
Name | Content example |
Task Relocation Due To Underlying Hardware Upgrade (Scheduled) | |
Task Relocation Due To Underlying Hardware Upgrade (Executing) | |
Task Relocation Due To Underlying Hardware Upgrade (Completed) | |
Task Relocation Due To Underlying Hardware Upgrade (Failed) | |
Task Relocation Due To Underlying Hardware Upgrade (Canceled) | |
Task Relocation Due To Underlying Hardware Upgrade (Pending Customer Action) | |