DataWorks:Intelligent monitoring

Alert notifications aren't arriving after I configure an alert rule

First, confirm whether an alert is actually being triggered — the fix depends on whether the alert fires but the notification fails, or whether the alert never fires at all.

The alert isn't being triggered

For auto triggered tasks, open the Cycle Instance page in Operation Center and check the instance status to see whether the alert conditions are met. For more information about the conditions for triggering a baseline alert, see Overview.

For real-time synchronization tasks, go to Operation Center and in the left-side navigation pane, choose Real-time Node O&M > Real-time Synchronization Nodes to check the task status.

One common reason alerts don't fire: when a task is incomplete, the system scans the previous 100 incomplete tasks. If a large number of tasks are frozen, the system may skip your task and no alert is triggered.

The alert fires, but you're not getting notifications

The fix depends on your notification channel.

How do I stop alerts for a specific task?

When a baseline is enabled, intelligent monitoring covers all tasks in the baseline and their ancestor tasks. Here's a quick example:

In this diagram, DataWorks has six tasks. Tasks D and E belong to a baseline, so intelligent monitoring watches Tasks A, B, D, and E (Tasks C and F are not monitored).

To stop alerts for a task in the baseline (D or E): ask the baseline owner to remove the task from the baseline.

To stop alerts for an ancestor task (A or B): the owners of Tasks D and E need to delete the dependency between their tasks and Task A or B. Because ancestor tasks can affect data generation in the baseline, monitoring is linked to those dependencies — removing the dependency removes the monitoring.

Why is a baseline in the Empty Baseline state?

Three scenarios can put a baseline into the Empty Baseline state:

1. All tasks were moved to another baseline. A task can belong to only one baseline. Adding a task to a different baseline removes it from the current one. If every task is removed, the baseline enters the Empty Baseline state.

2. The baseline was just created. On the day a baseline is created, it starts in the Empty Baseline state. After you enable it, the first baseline instance is generated the next day.

3. An invalid scheduling cycle is set for an hour-level baseline. If the scheduling cycle of an auto triggered instance doesn't match the expected cycles, the baseline can't generate instances correctly.

   For example, if a task runs at 6:00 and 18:00 every day, it has two cycles. Set 6:00 as the execution time for the first cycle and 18:00 for the second cycle.

Why is no alert sent when a baseline enters the Overtime state?

The Overtime state means tasks in the baseline didn't complete by the committed completion time — but this doesn't automatically trigger an alert.

Intelligent monitoring can only send an alert when it identifies which task caused the delay. If all tasks ran as expected and the baseline still enters the Overtime state, monitoring can't pinpoint a failing task, so no alert is sent. For more information, see Overview.

If this happens, check two things:

• The time configuration for the baseline — the committed completion time may not reflect actual task duration.

• The task dependency graph — an incorrect dependency can cause tasks to be sequenced in a way that makes on-time completion impossible.

Can I disable slowdown alerts for a task?

Intelligent monitoring only sends a slowdown alert when both conditions are true:

• The task is an ancestor task of an important task in a baseline.

• The task's runtime is significantly slower than its historical performance.

If a task meets both conditions and you receive a slowdown alert, check the Events tab in Operation Center to see which baseline tasks are affected. Then confirm the impact with the baseline owner.

• If the impact is minor, ignore the alert.

• If the impact is significant, investigate and optimize the task.

Why aren't I getting alerts for task errors?

Intelligent monitoring sends a task error alert only when at least one of the following is true:

• The task is an ancestor task of a task in an enabled baseline. See Manage baselines for details.

• A custom alert rule is configured for the task. See Create a custom alert rule to set one up.

How do I stop alert notifications at night?

1. Log on to the DataWorks console. In the top navigation bar, select the region. In the left-side navigation pane, choose Data Development and O&M > Operation Center. Select the workspace and click Go to Operation Center.

2. In the left-side navigation pane, click Smart Baseline, then click the Events tab.

3. Find the event triggering the night alert and choose one of the following:

   • Handle the event (temporarily disables the alert): Click Handle in the Actions column. In the Handle Event dialog box, configure the Handling Time and click OK. DataWorks records the handling operation and pauses alerts for the event while it's being handled.

   • Ignore the event (permanently disables the alert): Click Ignore in the Actions column, then click OK in the Ignore Event dialog. DataWorks records the operation and permanently disables alerts for this event.