All Products
Search
Document Center

Dataphin:Configure project monitoring and alert rules

Last Updated:Jun 23, 2026

Dataphin supports project-level monitoring and alerting. You can monitor all tasks in a project or configure monitoring in batches based on a combination of task type and scheduling type, helping you detect and handle task alerts quickly.

Limits

  • Monitoring and alerting can be configured only for Basic and Prod (production) projects.

  • A maximum of 100 project-level monitoring and alert rules are supported.

Procedure

  1. On the Dataphin home page, choose Develop > Task O&M from the top menu bar.

  2. In the navigation pane on the left, choose Monitoring Management > Offline Task Monitoring.

  3. On the Offline Task Monitoring page, click the Project Monitoring tab.

  4. On the Project Monitoring tab, click + New Project Monitoring.

  5. In the New Project Monitoring dialog box, configure the following parameters.

    Parameter

    Description

    Monitored Object

    Rule Name

    Enter a name for the rule. The name can be up to 36 characters long and can contain Chinese characters, letters, digits, underscores (_), and hyphens (-).

    Project

    Select the project to monitor. The drop-down list shows only projects for which you have the O&M - Access Folder permission.

    Monitoring Scope

    Select All Tasks in Project or Filter by Task Type.

    • All Tasks in Project: Monitors all tasks in the current project.

    • Filter by Task Type: Monitors tasks in the current project by a combination of task type and scheduling type.

      • Task Type: Includes Integration and Compute Tasks, Modeling Task, and All Task Types. If you set Task Type to Integration and Compute Tasks or Modeling Task, you can configure a sub-type. For the sub-type, you can select All or Custom. Modeling Task sub-types include Logical Dimension Table, Logical Fact Table, and Logical Summary Table. For Integration and Compute Tasks, the available sub-types vary by compute engine. Refer to the options on the page for details.

      • Scheduling Type: Includes Recurring Task, One-Time Task, and All Scheduling Types. If you set Scheduling Type to Recurring Task, you can configure the scheduling cycle. For the scheduling cycle, you can select All or Custom. Scheduling cycles include year, month, week, day, hour, and minute.

    Important
    • Project monitoring applies to all objects within the specified monitoring scope. New tasks that meet the criteria are automatically configured with the corresponding monitoring job.

    • If a monitored object has both project-level and task-level monitoring configured with the same recipient and notification method, the task-level alert configuration takes precedence. For more information, see Alert rule priorities.

    Alarm Reason

    Alert Condition

    Configure alerts for tasks that have an Error, are Not Finished, or have a Timeout. To add more alert conditions, click + New Alert Condition.

    • Error: Triggers an alert if a task encounters a runtime error, or if any field in a logical table has an error.

      Note

      Dataphin automatically retries failed tasks. An alert is triggered only after all retry attempts are exhausted.

    • Not Finished: Set the object type and the time point as the trigger condition. An alert is triggered if the task is not finished by the specified time. You can monitor Daily/Weekly/Monthly Scheduled Tasks or Hourly/Minutely Scheduled Tasks. Select at least one type.

      Note

      Changes to an incomplete alert configuration will not take effect until the next day.

      • Daily/Weekly/Monthly Scheduled Tasks: Triggers an alert if the task is not finished within the configured Trigger Condition time. The trigger condition uses the same time zone as the Monitoring Interval parameter. For more information, see the Monitoring Interval description below.

      • Hourly/Minutely Scheduled Tasks: The trigger condition can be Not finished after a specific time or Instance not finished after scheduled runtime.

        • Not finished after a specific time: For a specified cycle of a monitored hourly or minutely scheduled task, triggers an alert if the task is not finished after the specified time. The cycle range is 1 to 288 cycles. To add multiple cycles, click + Add Cycle. You can add up to 24 non-overlapping cycles. The Monitoring Time Point uses the same time zone as the Monitoring Interval parameter. For more information, see the Monitoring Interval description below.

        • Instance not finished after scheduled runtime: For a specified monitoring cycle of a monitored hourly or minutely scheduled task, triggers an alert if the instance is not finished after the specified time following its scheduled runtime. For the monitoring cycle range, select All, First Cycle, Last Cycle, or Custom. The cycle range is 1 to 288 cycles.

          Important
          • For Not Finished alerts, changing the scheduling cycle of a monitoring job to hourly or minutely may cause the corresponding monitoring rule to become invalid.

          • An alert is triggered if an unfinished field exists in a logical table at a specified time point. This is valid only for daily tasks.

    • Timeout: Set the timeout duration. Valid range: 0 to 19,999 minutes. Values outside this range are clamped to the nearest valid value. The timer starts when the instance status changes to Running. An alert is triggered if the task or a field in a logical table is not finished after the specified duration.

    Monitoring Interval

    Set the active monitoring period. Select All Day or Specified Period. For a specified period, configure a Start Time and an End Time.

    If the system time zone, which is the time zone in the User Center, is different from the scheduling time zone, both time zones are displayed. When you select a start time for a specified period, the system automatically calculates the corresponding time in the scheduling time zone. If the calculated time in the scheduling time zone is on a different day than the system time zone, (-1) indicates the previous day and (+1) indicates the next day. For example, if the system time zone is GMT+08:00 and the scheduling time zone is GMT+01:00, and you configure the period as 00:00 ~ 01:00, the corresponding time in the scheduling time zone is 17:00(-1) ~ 18:00(-1).

    Alert Frequency

    How often alert notifications are sent. Valid range: 1 to 59 minutes per alert. Values outside this range are clamped to the nearest valid value.

    Send Count

    How many times an alert notification is sent per trigger. Valid range: 1 to 10. Values outside this range are clamped to the nearest valid value.

    Accept Configuration

    Configure alert recipients. Select Owner, Duty Schedule, or Custom. To add more recipients, click New Recipient.

    • Owner: The owner of the task.

    • Duty Schedule: The on-call schedule configured in the Alert Center. You must create an on-call schedule in advance. For more information, see Manage on-call schedules.

    • Custom: Sends alerts to non-owners and users not on the on-call schedule, such as project administrators.

    Notification Method: You can select Phone, Text Message, Email, DingTalk, Lark, WeCom, and Custom Channel.

    Important

    Ensure the recipient has a valid contact method configured. For more information, see Add, configure, and manage Dataphin members.

  6. Click OK to complete the project monitoring and alert configuration.

What to do next

View all alert events in the Alert Center. For more information, see Alert events.