Notification management

更新时间:
复制 MD 格式

By default, DMS enables status notifications for various ticket types and task flows. You can customize recipients to ensure notifications are delivered effectively. This topic describes how to manage notifications.

Prerequisites

You must have the Administrator or DBA user role. For more information, see System roles.

Background information

You may want to receive timely status updates for events such as permission applications, schema changes, or failed task flow executions.

In addition to DingTalk notifications, DMS supports multiple notification methods, including text messages, emails, and DingTalk chatbot webhooks.

The default recipient is the submitter of the ticket or task flow, except for tickets pending approval, where the recipient is the approver. For more information about supported event types, see Event types.

Configure notifications

You can subscribe to message events from different feature modules and specify notification recipients for each event.

  1. Log in to DMS 5.0.

  2. In the top navigation bar, choose O&M > Notification.

  3. The Notification Management page lists your configured notifications. You can then perform the following operations.

    • Customize notification recipients

      1. Find the target notification and click Modify in the Operation column.

        Note

        You can also quickly select Optional notification role in the Optional notification role column on the right side of the target message notification row.

      2. In the dialog box, select recipients from Optional notification role or Additional notification User.

        You can configure the following types of notification recipients:

        • Default notification role: The system automatically assigns a default recipient based on the message type and status.

          For tickets pending approval, the recipient is the approver. For all other statuses, the recipient is the submitter.

        • Optional notification role: The system provides a list of relevant roles based on the message type.

          These roles typically include submitter, approver, Data Owner, Instance DBA, DBA, Administrator, and Security Administrator.

        • Additional notification User: You can select any user within your tenant to receive additional notifications.

          For example, if a developer submits a schema design change, big data developers may need to be notified immediately to synchronize their work. This helps prevent reporting anomalies caused by a lack of synchronization.

      3. Click Confirm.

        When the event occurs, the specified recipients will receive notifications. You can also configure multiple notification methods. For more information, see Configure personal information and notification methods.

    • Disable a notification

      To disable notifications for a specific event type, find the event and turn off its Status switch.

      Once disabled, you will no longer receive notifications for that event type.

    • Enable or disable notifications in bulk

      You can enable or disable multiple notifications at once.

      1. Select the checkboxes of the target notifications.

      2. At the top of the page, click Batch enable or Batch disable.

Event types

DMS can send notifications for the following event types:

Feature

Category

Status

Tickets

permission application

  • Pending approval

  • Approved

  • Rejected

data change

  • Precheck failed

  • Pending submission

  • Pending approval

  • Approved

  • Rejected

  • Execution successful

  • Execution failed

  • Pending scheduling

  • Scheduling timed out

data export

  • Precheck failed

  • Pending submission

  • Pending approval

  • Approved

  • Rejected

  • Export successful

  • Export failed

data tracking

  • File retrieval failed

  • Pending submission

  • Pending approval

  • Approved

  • Rejected

  • Log processing successful

  • Log processing failed

database clone

  • Pending approval

  • Approved

  • Rejected

  • Clone successful

  • Clone failed

test data generation

  • Pending approval

  • Approved

  • Rejected

  • Generation successful

  • Generation failed

schema design

  • Table schema changed

  • Pending approval

  • Approved

  • Rejected

  • Execution successful

  • Execution failed

table synchronization

  • Precheck failed

  • Pending submission

  • Pending approval

  • Approved

  • Rejected

  • Execution successful

  • Execution failed

SQL review

  • Check passed

  • Check failed

  • Manually approved/rejected

  • Parsing error

  • Pending analysis

task orchestration

task flow

  • Execution successful

  • Execution failed

data warehouse development

task flow

  • Execution successful

  • Execution failed