Subscribe to DTS event notifications - Data Transmission Service

Data Transmission Service (DTS) integrates with CloudMonitor — a service that monitors Internet applications and Alibaba Cloud resources — to send alert notifications when task events occur. Configure a subscription policy to get notified of task anomalies, recoveries, and planned maintenance events so you can respond quickly when issues arise.

Notification channels

CloudMonitor routes event notifications through the following channels:

Email, SMS, or DingTalk chatbot — direct notification to on-call contacts
Push to a service endpoint — automated handling via Simple Message Queue (formerly MNS), Function Compute, Simple Log Service, or a callback URL

Prerequisites

Before you begin, ensure that you have:

ApsaraDB Fault or Maintenance Notifications enabled in the Message Center console, with an O&M engineer set as the contact
Alert contacts and alert contact groups created in CloudMonitor, with the contacts added to the groups. For instructions, see Create an alert contact or an alert contact group

Create a subscription policy

Log on to the CloudMonitor console.
In the left-side navigation pane, choose Event Center > Event Subscription.
Note
If the Event Subscription page is not displayed, see Set alert rules for DTS tasks in the CloudMonitor console.
If 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 based on the subscription type: For all other parameters, see Subscription policy parameters.
- System Events (recommended for task status alerts): Set Subscription Type to System Events, then set Products to Data Transmission Service in the Subscription Scope section. > Note: For a list of system events that DTS supports, see System events.
- Threshold Events (for metric-based alerts): Set Subscription Type to Threshold Events, then search for DTS in the Product Classification section and select the relevant option.
Click Submit.

To view, modify, or delete a subscription policy, see Manage event subscription policies (recommended).

Debug an event subscription

Use the debug feature to send a test notification and verify that the alert delivery chain is working.

Log on to the CloudMonitor console.
In the left-side navigation pane, choose Event Center > Event Subscription.
If the Event Subscription page is not displayed, see Set alert rules for DTS tasks in the CloudMonitor console.
On the Subscription Policy tab, click Debug Event Subscription.
In the Create Event Debugging panel, configure the debug event:
1. Set Products to Data Transmission Service.
2. Select a Name from the list. > Note: > - Name corresponds to the NameDesc parameter of the system event. > - The Task Relocation Due To Underlying Hardware Upgrade series and Instance Task Latency events cannot be debugged.
3. Review the debug content that CloudMonitor generates automatically in JSON format. Modify the fields as needed. For field descriptions and examples, see Event content examples below.
Click OK.

CloudMonitor sends a test alert notification to all contacts in the subscription policy based on the notification methods specified. The Operation successful message confirms that the test was triggered.

Event content examples

DTS publishes three categories of events, each with a different JSON structure. The sections below describe the fields and provide examples for each category.

Synchronization, migration, and tracking tasks

These events follow a flat JSON structure with a small set of fields.

Parameters

Parameter	Description	Example value
`product`	The cloud product that the event belongs to (Product).	`DTS`
`resourceId`	The affected resource. The value starts with `acs:dts:` and includes the instance region, Alibaba Cloud account ID, and instance ID.	`acs:dts:cn-hangzhou:135218574272:instance/dtsb1gx8vo2265`
`level`	The severity level of the event (Level): `CRITICAL` for anomalies, `INFO` for recoveries.	`INFO`
`instanceName`	The name of the affected instance, in the format `<Task ID>/<Instance Name>`.	`f1es8k10220****/testsync`
`regionId`	The region where the instance runs.	`cn-hangzhou`
`name`	The system event name (Name).	`sync_job_restore`
`content`	The event content. For tracking task recovery events, this field contains a nested object with a `msg` key.	`testcontent`
`status`	The event status (Status): `failed` for anomalies, `restore` for recoveries.	`restore`

Examples

The table below shows paired examples for each task type — one for the anomaly event and one for the recovery event.

Event	Content example
Synchronization task abnormal	`{"product":"DTS","resourceId":"acs:dts:cn-hangzhou:135216572282:instance/dtsb1gx8vo2265","level":"CRITICAL","instanceName":"f1es8k10220/testsync","regionId":"cn-hangzhou","name":"sync_job_abnormal","content":"testcontent","status":"failed"}`
Synchronization task recovered	`{"product":"DTS","resourceId":"acs:dts:cn-hangzhou:135216572282:instance/dtsb1gx8vo2265","level":"INFO","instanceName":"f1es8k10220/testsync","regionId":"cn-hangzhou","name":"sync_job_restore","content":"testcontent","status":"restore"}`
Migration task abnormal	`{"product":"DTS","resourceId":"acs:dts:cn-hangzhou:135216572282:instance/dtsb1ah8a7x259","level":"CRITICAL","instanceName":"q2rb8x0022p/testmigrate","regionId":"cn-hangzhou","name":"migration_job_abnormal","content":"testcontent","status":"failed"}`
Migration task recovered	`{"product":"DTS","resourceId":"acs:dts:cn-hangzhou:135216572282:instance/dtsb1ah8a7x259","level":"INFO","instanceName":"q2rb8x0022p/testmigrate","regionId":"cn-hangzhou","name":"migration_job_restore","content":"testcontent","status":"restore"}`
Tracking task abnormal	`{"product":"DTS","resourceId":"acs:dts:cn-hangzhou:135216572282:instance/dtsktuw8d7n252","level":"CRITICAL","instanceName":"qgkm8okq25q/testsubscribe","regionId":"cn-hangzhou","name":"subscribe_job_abnormal","content":"testcontent","status":"failed"}`
Tracking task recovered	`{"product":"DTS","resourceId":"acs:dts:cn-hangzhou:135216572282:instance/dtsktuw8d7n252","level":"INFO","instanceName":"qgkm8okq25q/testsubscribe","regionId":"cn-hangzhou","name":"subscribe_job_restore","content":{"msg":"testcontent"},"status":"restore"}`

For the full formatted JSON, expand each event below.

<details> <summary>Synchronization task abnormal</summary>

{
    "product": "DTS",
    "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsb1gx8vo2265****",
    "level": "CRITICAL",
    "instanceName": "f1es8k10220****/testsync",
    "regionId": "cn-hangzhou",
    "name": "sync_job_abnormal",
    "content": "testcontent",
    "status": "failed"
}

</details>

<details> <summary>Synchronization task recovered</summary>

{
    "product": "DTS",
    "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsb1gx8vo2265****",
    "level": "INFO",
    "instanceName": "f1es8k10220****/testsync",
    "regionId": "cn-hangzhou",
    "name": "sync_job_restore",
    "content": "testcontent",
    "status": "restore"
}

</details>

<details> <summary>Migration task abnormal</summary>

{
    "product": "DTS",
    "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsb1ah8a7x259****",
    "level": "CRITICAL",
    "instanceName": "q2rb8x0022p****/testmigrate",
    "regionId": "cn-hangzhou",
    "name": "migration_job_abnormal",
    "content": "testcontent",
    "status": "failed"
}

</details>

<details> <summary>Migration task recovered</summary>

{
    "product": "DTS",
    "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsb1ah8a7x259****",
    "level": "INFO",
    "instanceName": "q2rb8x0022p****/testmigrate",
    "regionId": "cn-hangzhou",
    "name": "migration_job_restore",
    "content": "testcontent",
    "status": "restore"
}

</details>

<details> <summary>Tracking task abnormal</summary>

{
    "product": "DTS",
    "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsktuw8d7n252****",
    "level": "CRITICAL",
    "instanceName": "qgkm8okq25q****/testsubscribe",
    "regionId": "cn-hangzhou",
    "name": "subscribe_job_abnormal",
    "content": "testcontent",
    "status": "failed"
}

</details>

<details> <summary>Tracking task recovered</summary>

{
    "product": "DTS",
    "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsktuw8d7n252****",
    "level": "INFO",
    "instanceName": "qgkm8okq25q****/testsubscribe",
    "regionId": "cn-hangzhou",
    "name": "subscribe_job_restore",
    "content": {
        "msg": "testcontent"
    },
    "status": "restore"
}

</details>

Instance tasks

Instance task events have a more complex structure. The event payload includes an outer envelope with standard fields and a nested content object that carries detailed event data.

The level for all instance task exception events is always WARN. The status field indicates whether the exception is ongoing (Executing) or resolved (Executed).

Parameters

Outer fields

Parameter	Description	Example value
`product`	The cloud product that the event belongs to (Product).	`DTS`
`resourceId`	The affected resource. The value starts with `dts:` and includes the instance region, Alibaba Cloud account ID, and instance ID.	`dts:cn-hangzhou:135216572282:instance/dtsb1gx8vo2265`
`level`	The severity level (Level). Always `WARN` for instance task exceptions.	`WARN`
`instanceName`	The name of the affected instance, in the format `<Task ID>/<Instance Name>`.	`f1es8k10220****/testsync`
`regionId`	The region where the instance runs.	`cn-hangzhou`
`name`	The system event name (Name).	`Instance:JobStatus.Abnormal:Executing`
`status`	The event status (Status): `Executing` for ongoing exceptions, `Executed` for recovered exceptions.	`Executed`

`content` object fields

Parameter	Description	Example value
`eventId`	The ID of the system event.	`37d28e238b151a0d44dfdf1f2153****`
`publishTime`	The time when the event was published (UTC+8).	`2025-08-26T14:40:05+08:00`
`reason`	The reason why the event was triggered.	`testreason`
`product`	The cloud product that the event belongs to.	`dts`
`instanceComment`	The ID of the affected instance.	`dtsb1gx8vo2265****`
`instanceId`	The ID of the affected instance.	`dtsb1gx8vo2265****`
`instanceType`	The resource type: `Instance`, `Host`, or `User`.	`Instance`
`eventType`	The event category (EventType). Always `Exception` for instance task exceptions.	`Exception`
`extra`	Additional event details. Contains `eventTime`, `cloudEvent`, and `region`.	—

`content.extra.cloudEvent.data` fields

Parameter	Description	Example value
`gmtModified`	The time when the event record was last updated (UTC).	`2025-08-26T06:39:56Z`
`gmtCreated`	The time when the event record was created (UTC).	`2025-08-26T06:39:37Z`
`eventCategory`	The event category (EventType). Always `Exception` for instance task exceptions.	`Exception`
`detailReason`	The detailed reason why the event was triggered.	`****`
`uid`	The Alibaba Cloud account ID.	`135216572282****`
`cmsProduct`	The cloud product that the event belongs to.	`DTS`
`instanceId`	The ID of the affected instance.	`dtsb1gx8vo2265****`
`eventLevel`	The severity level (Level). Always `WARN` for instance task exceptions.	`WARN`
`handleStatus`	The processing status of the event.	`None`
`startTime`	The start time of the event (UTC).	`2025-08-26T06:38:17Z`
`endTime`	The end time of the event (UTC).	`2025-08-26T06:38:17Z`
`detailImpact`	A pagination parameter.	`-`
`eventId`	The ID of the event.	`e-0mqwjyhomzrb32****`
`product`	The cloud product that the event belongs to.	`dts`
`dbType`	The database type.	`****`
`hasLifeCycle`	Whether the event has a lifecycle: `0` (no lifecycle) or `1` (has lifecycle).	`0`
`eventType`	The event type.	`JobStatus`
`eventReason`	The source of the event.	`JobStatus.Abnormal`
`eventImpact`	The impact of the event.	`Abnormal`
`mainEventId`	The ID of the main event.	`e-0mqwjyhomzrb3i****`
`eventCode`	The event code, which matches the `name` field value.	`Instance:JobStatus.Abnormal:Executing`
`isClosed`	Whether the event is closed: `0` (closed) or `1` (open).	`1`
`regionId`	The region where the instance runs.	`cn-hangzhou`
`sourceType`	The source data type.	`DBaaS`
`eventStatus`	The event status: `Executing` (ongoing exception) or `Executed` (recovered).	`Executed`
`eventDetail`	Details of the event, including task type (`dts_task_type`), task ID (`dts_job_id`), task status (`job_state`), error code (`err_code`), and error details (`err_msg_detail`, `message`).	`****`
`resourceType`	The resource type: `Instance`, `Host`, or `User`.	`Instance`

CloudEvents envelope fields (inside `content.extra.cloudEvent`)

Parameter	Description	Example value
`subject`	The affected resource. The value starts with `acs:dts:`.	`acsnce/dts65u`
`specversion`	The CloudEvents protocol version.	`1.0`
`time`	The time when the event was created (UTC).	`2025-08-25T20:59:32Z`
`source`	The event source.	`acs:dts:dts`
`id`	The CloudEvents event ID.	`e-0mqwjyhomzrb32****`
`region`	The region where the instance runs.	`cn-hangzhou`
`type`	The event type.	`Instance:JobStatus.Abnormal`

Examples

<details> <summary>Instance task exception started</summary>

{
    "product": "DTS",
    "resourceId": "dts:cn-hangzhou:135216572282****:instance/dtsb1gx8vo2265****",
    "level": "WARN",
    "instanceName": "f1es8k10220****/testsync",
    "regionId": "cn-hangzhou",
    "name": "Instance:JobStatus.Abnormal:Executing",
    "content": {
        "eventId": "f88***4b3",
        "publishTime": "2025-08-26T05:03:38+08:00",
        "reason": "testreason",
        "product": "***",
        "instanceComment": "dts***b9n",
        "instanceId": "dts***b9n",
        "extra": {
            "eventTime": "2025-08-26T05:02:13+08:00",
            "cloudEvent": {
                "data": {
                    "gmtModified": "202***25Z",
                    "eventCategory": "Ex***on",
                    "gmtCreated": "202***25Z",
                    "detailReason": "***",
                    "uid": "125***870",
                    "cmsProduct": "***",
                    "instanceId": "dts***b9n",
                    "eventLevel": "WA***",
                    "handleStatus": "No***",
                    "startTime": "2025-08-25T21:02:13Z",
                    "detailImpact": "***",
                    "eventId": "e-0***ypw",
                    "product": "***",
                    "dbType": "***",
                    "hasLifeCycle": 123456,
                    "eventType": "Jo***us",
                    "eventReason": "Job***mal",
                    "eventImpact": "Ab***al",
                    "mainEventId": "e-0***cua",
                    "eventCode": "Ins***ing",
                    "isClosed": 123456,
                    "regionId": "cn-***hou",
                    "sourceType": "DB***",
                    "eventStatus": "Ex***ng",
                    "endTime": "2025-08-25T21:02:13Z",
                    "eventDetail": "****",
                    "resourceType": "In***ce"
                },
                "subject": "acs***nce/dts***b9n",
                "specversion": "***",
                "time": "2025-08-25T21:03:25Z",
                "source": "acs***dts",
                "id": "e-0***ypw",
                "region": "cn-***hou",
                "type": "Ins***mal"
            },
            "region": "cn-hangzhou"
        },
        "instanceType": "In***ce",
        "eventType": "Ex***on"
    },
    "status": "Executing"
}

</details>

<details> <summary>Instance task exception recovered</summary>

{
    "product": "DTS",
    "resourceId": "dts:cn-hangzhou:135216572282****:instance/dtsb1gx8vo2265****",
    "level": "WARN",
    "instanceName": "f1es8k10220****/testsync",
    "regionId": "cn-hangzhou",
    "name": "Instance:JobStatus.Abnormal:Executed",
    "content": {
        "eventId": "b9b***3ae",
        "publishTime": "2025-08-26T04:59:37+08:00",
        "reason": "testreason",
        "product": "dts",
        "instanceComment": "dts***65u",
        "instanceId": "dts***65u",
        "extra": {
            "eventTime": "2025-08-26T04:21:37+08:00",
            "cloudEvent": {
                "data": {
                    "gmtModified": "202***32Z",
                    "eventCategory": "Ex***on",
                    "gmtCreated": "202***32Z",
                    "detailReason": "***",
                    "uid": "113***735",
                    "cmsProduct": "***",
                    "instanceId": "dts***65u",
                    "eventLevel": "WA***",
                    "handleStatus": "No***",
                    "startTime": "2025-08-25T20:21:37Z",
                    "detailImpact": "***",
                    "eventId": "e-0***iue",
                    "product": "***",
                    "dbType": "***",
                    "hasLifeCycle": 123456,
                    "eventType": "Jo***us",
                    "eventReason": "Job***mal",
                    "eventImpact": "Ab***al",
                    "mainEventId": "e-0***gd8",
                    "eventCode": "Ins***ted",
                    "isClosed": 123456,
                    "regionId": "cn***ng",
                    "sourceType": "DB***",
                    "eventStatus": "Ex***ed",
                    "endTime": "2025-08-25T20:21:37Z",
                    "eventDetail": "****",
                    "resourceType": "In***ce"
                },
                "subject": "acs***nce/dts***65u",
                "specversion": "***",
                "time": "2025-08-25T20:59:32Z",
                "source": "acs***dts",
                "id": "e-0***iue",
                "region": "cn***ng",
                "type": "Ins***mal"
            },
            "region": "cn-hangzhou"
        },
        "instanceType": "In***ce",
        "eventType": "Ex***on"
    },
    "status": "Executed"
}

</details>

Task relocation due to underlying hardware upgrade

These events are triggered when DTS relocates a task during planned infrastructure maintenance. The instanceName field uses the format <Instance ID>/<Instance Name> (not <Task ID>/<Instance Name> as in other task types).

The status field tracks the full lifecycle of the relocation: Scheduled → Executing → Executed (or Failed, Canceled, ToDealt).

The Task Relocation Due To Underlying Hardware Upgrade series cannot be debugged using the debug feature.

Parameters

Parameter	Description	Example value
`product`	The cloud product that the event belongs to (Product).	`DTS`
`userId`	The Alibaba Cloud account ID.	`135216572282****`
`level`	The severity level (Level): `CRITICAL` for Scheduled, Failed, and ToDealt; `INFO` for Executing, Executed, and Canceled.	`INFO`
`resourceId`	The affected resource. The value starts with `acs:dts:`.	`acs:dts:cn-hangzhou:135216572282:instance/dtsmq5j38bn28n`
`instanceName`	The name of the affected instance, in the format `<Instance ID>/<Instance Name>`.	`dtsmq5j38bn28n****/test`
`dryRun`	Whether this is a dry run: `true` (dry run only) or `false` (normal request).	`false`
`ver`	The CloudEvents protocol version.	`1.0`
`trace`	The request ID.	`54ee8594-5ec4-408a-93ce-c8fbb433****`
`name`	The system event name (Name).	`Instance:SystemMaintenance.Shift:Executed`
`regionId`	The region where the instance runs.	`cn-hangzhou`
`status`	The event status (Status): `Scheduled`, `Executing`, `Executed`, `Failed`, `Canceled`, or `ToDealt` (pending customer action).	`Executed`
`time`	The time when the event was generated.	`Aug 22, 2025 5:39:51 PM`
`content`	The event content. May include the task or instance name (`jobName`), estimated running time (`innerScheduleTime`), instance ID (`instanceId`), and instance region (`region`).	`testcontent`

Examples

<details> <summary>Scheduled</summary>

{
  "product": "DTS",
  "userId": "135216572282****",
  "level": "CRITICAL",
  "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsmq5j38bn28n****",
  "instanceName": "dtsmq5j38bn28n****/testinstance",
  "dryRun": false,
  "ver": "1.0",
  "trace": "54ee8594-5ec4-408a-93ce-c8fbb433****",
  "name": "Instance:SystemMaintenance.Shift:Scheduled",
  "regionId": "cn-hangzhou",
  "status": "Scheduled",
  "time": "Aug 22, 2025 5:39:51 PM",
  "content": "testcontent"
}

</details>

<details> <summary>Executing</summary>

{
  "product": "DTS",
  "userId": "135216572282****",
  "level": "INFO",
  "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsmq5j38bn28n****",
  "instanceName": "dtsmq5j38bn28n****/testinstance",
  "dryRun": false,
  "ver": "1.0",
  "trace": "55ee8594-5ec4-408a-93ce-c8fac56****",
  "name": "Instance:SystemMaintenance.Shift:Executing",
  "regionId": "cn-hangzhou",
  "status": "Executing",
  "time": "Aug 22, 2025 5:39:51 PM",
  "content": "testcontent"
}

</details>

<details> <summary>Completed</summary>

{
  "product": "DTS",
  "userId": "135216572282****",
  "level": "INFO",
  "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsmq5j38bn28n****",
  "instanceName": "dtsmq5j38bn28n****/testinstance",
  "dryRun": false,
  "ver": "1.0",
  "trace": "56ee8594-5ec4-408a-93ce-c8fbac58****",
  "name": "Instance:SystemMaintenance.Shift:Executed",
  "regionId": "cn-hangzhou",
  "status": "Executed",
  "time": "Aug 22, 2025 5:39:51 PM",
  "content": "testcontent"
}

</details>

<details> <summary>Failed</summary>

{
  "product": "DTS",
  "userId": "135216572282****",
  "level": "CRITICAL",
  "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsmq5j38bn28n****",
  "instanceName": "dtsmq5j38bn28n****/testinstance",
  "dryRun": false,
  "ver": "1.0",
  "trace": "57ee8594-5ec4-408a-93ce-c8fac59****",
  "name": "Instance:SystemMaintenance.Shift:Failed",
  "regionId": "cn-hangzhou",
  "status": "Failed",
  "time": "Aug 22, 2025 5:39:51 PM",
  "content": "testcontent"
}

</details>

<details> <summary>Canceled</summary>

{
  "product": "DTS",
  "userId": "135216572282****",
  "level": "INFO",
  "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsmq5j38bn28n****",
  "instanceName": "dtsmq5j38bn28n****/testinstance",
  "dryRun": false,
  "ver": "1.0",
  "trace": "54ee8594-5ec4-408a-93ce-c8fbb433****",
  "name": "IInstance:SystemMaintenance.Shift:Canceled",
  "regionId": "cn-hangzhou",
  "status": "Canceled",
  "time": "Aug 22, 2025 5:39:51 PM",
  "content": "testcontent"
}

</details>

<details> <summary>Pending customer action</summary>

{
  "product": "DTS",
  "userId": "135216572282****",
  "level": "CRITICAL",
  "resourceId": "acs:dts:cn-hangzhou:135216572282****:instance/dtsmq5j38bn28n****",
  "instanceName": "dtsmq5j38bn28n****/testinstance",
  "dryRun": false,
  "ver": "1.0",
  "trace": "54ee8594-5ec4-408a-93ce-c8fbb433****",
  "name": "Instance:SystemMaintenance.Shift:ToDealt",
  "regionId": "cn-hangzhou",
  "status": "ToDealt",
  "time": "Aug 22, 2025 5:39:51 PM",
  "content": "testcontent"
}

</details>

What's next

Manage event subscription policies (recommended) — view, modify, or delete existing policies
Set alert rules for DTS tasks in the CloudMonitor console — configure threshold-based alert rules
Create an alert contact or an alert contact group — manage who receives notifications