This topic provides answers to frequently asked questions about the intelligent monitoring module.

What can I do if I am unable to receive alert notifications after I configure an alert in Operation Center?

Check whether the alert is triggered. If the alert is triggered but you cannot receive alert notifications, troubleshoot the issue based on the notification method that you configure. The notification methods include text message, email, and DingTalk group message.

  • Check whether the alert is triggered
    • If the alert is configured for an auto triggered node, check the status of the node instances on the Cycle Instance page in Operation Center and whether the alert can be triggered for the node.

      For more information about the conditions for triggering a custom alert, see Manage custom alert rules. For more information about the conditions for triggering a baseline alert, see Monitor.

    • If the alert is configured for a real-time synchronization node, check the status of the real-time synchronization node. To do so, go to Operation Center and choose RealTime Task Maintenance > Real Time DI in the left-side navigation pane.
  • Failed to receive alert notifications in text messages or emails after the alert is triggered

    Check whether the phone numbers and email addresses of alert contacts are properly configured in DataWorks.

    On the homepage of the DataWorks console, choose Alerts > Alert Contacts in the left-side navigation pane. On the Alert Contacts page, you can view and configure alert contacts. The following figure shows the steps.

    Configure alert contactsIf the specified alert contacts cannot receive alert notifications after the alert is triggered, perform the following checks on the Alert Contacts page:
    • Check whether the phone numbers and email addresses of the alert contacts are configured.
    • Check whether the alert contacts activate the phone numbers and email addresses that have been configured.
    Note
    • Alibaba Cloud accounts and RAM users that are granted the AliyunDataWorksFullAccess permission can configure contact information for RAM users. For more information, see Configure and view alert contacts.
    • If the phone numbers or email addresses of the alert contacts are not properly configured, the system sends alert notifications to the recipients that are listed on the Common Settings page. As a result, the specified alert contacts cannot receive the alert notifications.
  • Failed to receive alert notifications in DingTalk groups after the alert is triggered

    Perform the following checks:

    • Check whether the webhook URL of the DingTalk chatbot is correct on the alert configuration page
      • If the alert is configured for an auto triggered node, check whether the webhook URL is valid. For example, check for extra spaces.
      • If the alert is configured for a real-time synchronization node, check whether the token information of the DingTalk chatbot is correct. Configure an alert for a real-time synchronization node
    • Check whether the DingTalk chatbot is correctly configured

      When you add a chatbot to the DingTalk group for receiving alert notifications, set the Security Settings parameter to Custom Keywords and make sure that the keywords include DataWorks. For more information, see the "Send alert notifications to a DingTalk group" section of the Manage custom alert rules topic.

What can I do if I want to disable alerting for a node?

After a baseline is created and enabled, the intelligent monitoring module monitors all nodes in the baseline and their ancestor nodes. If a node in the baseline or an ancestor node of the baseline affects data generation of the monitored nodes in the baseline, the intelligent monitoring module sends an alert notification to the node owner. For more information, see Monitor. 1
In the example shown in the preceding figure, DataWorks has six nodes, and Nodes D and E belong to a baseline. The intelligent monitoring module monitors Nodes D and E and all their ancestor nodes. In this case, the intelligent monitoring module detects errors or slowdowns on Node A, B, D, or E. Nodes C and F are not monitored by the intelligent monitoring module.
  • If you want to disable alerting for Nodes D and E, contact the baseline owner to remove Nodes D and E from the baseline.
  • Nodes A and B are ancestor nodes of Nodes D and E and may affect data generation of the monitored nodes in the baseline. If an error or a slowdown occurs on Node A or B, the intelligent monitoring module sends an alert notification to the node owner.

    If you want to disable alerting for Node A or B, contact the owners of Nodes D and E to delete the dependency of Nodes D and E on Node A or B.

Why is a baseline in the Empty Baseline state?

In the following scenarios, a baseline may enter the Empty Baseline state:

  • Scenario 1: A node can belong to only one baseline. If you add a node to another baseline, the system removes the node from the current baseline and adds it to the specified baseline. If all nodes are removed from a baseline, the baseline enters the Empty Baseline state.
  • Scenario 2: On the day when a baseline is created, the baseline is in the Empty Baseline state. After you enable the baseline, a baseline instance is generated on the next day.
  • Scenario 3: You specify an invalid point in time as the baseline time for an auto triggered node instance in an hour-level baseline.
    Note For example, the node is scheduled to run at 6:00 and 18:00 every day. However, you specify 6:00 and 18:00 as the baseline time when you create a baseline and add the node to the baseline.

Why is no alert notification sent for a baseline in the Overtime state?

Baseline monitoring is controlled by the baseline switch and enabled for nodes. Overtime is a baseline state, which indicates that the nodes in a baseline are not complete when the baseline time is reached. If all nodes in a baseline are run as expected, no alert is triggered even if the baseline enters the Overtime state. This is because the intelligent monitoring module cannot determine which node has an error.

If the baseline enters the Overtime state when all nodes are run as expected, consider the following reasons:
  • The baseline time is improper.
  • The node dependency is improper.

Can I disable alerting for a node that slows down?

The intelligent monitoring module notifies you of a node slowdown only if a node meets both of the following conditions:
  • The node is an ancestor node of an important baseline.
  • Compared with its historical performance, the node does slow down.
You can view the descendant baseline affected by the node on the Event management tab in Operation Center. Then, you can confirm the impact with the party whose baseline contains descendant nodes of your node.
  • If the node slowdown has a minor impact, you can disable alerting.
  • If the node slowdown has a major impact, maintain your node properly.

Why am I unable to receive an alert notification for a node error?

The intelligent monitoring module notifies you of a node error only if a node meets one of the following conditions:
  • The node is an ancestor node of a baseline that is enabled. For more information about baselines, see Manage baselines.
  • A custom alert rule is configured. For more information about how to configure a custom alert rule, see Manage custom alert rules.

What can I do if I receive an alert notification at night?

  1. Go to the DataStudio page.
    1. Log on to the DataWorks console.
    2. In the left-side navigation pane, click Workspaces.
    3. In the top navigation bar, select the region in which the workspace that you want to manage resides. Find the workspace and click DataStudio in the Actions column.
  2. On the DataStudio page, click the Icon icon in the upper-left corner and choose All Products > Data Development And Task Operation > Operation Center.
  3. In the left-side navigation pane, choose Alarm > Smart Baseline > Event management.
  4. On the Event management tab, disable alerting. You can disable alerting in one of the following ways:
    • Handle the event that triggers the alert. Then, alerting is temporarily disabled for the event.
      1. Find the event and click Handle in the Operation column.
      2. In the Handle Event dialog box, set the Handling Time parameter.
      3. Click OK.
        Note DataWorks records the event handling operation and pauses alerting for the event when the event is being handled.
    • Ignore the event that triggers the alert. Then, alerting is permanently disabled for the event.
      1. Find the event and click Ignore in the Operation column.
      2. In the Ignore Event message, click OK.
        Note DataWorks records the event ignoring operation and permanently stops alerting for the event.