All Products
Search
Document Center

DataWorks:Trigger event checking in Operation Center

Last Updated:Nov 14, 2024

After you register, publish, and enable an extension in DataWorks Open Platform, the extension takes effect. When you perform an operation that triggers an extension point event on a service page of a workspace for which an extension takes effect, DataWorks sends an event message to your extension. Then, the extension checks the extension point event. You can view the result returned by the extension. This topic describes the extension point events that are supported by Operation Center and how to use extension points to trigger an extension to check events.

Prerequisites

Background information

DataWorks can send messages for extension point events to extensions. To check extension point events, you can enable extensions that relate to the extension point events based on the extension points supported by DataWorks. You can also customize the processing logic of extension point events by using extensions. To implement the preceding features, you need to register an extension in the DataWorks console and go to the Extension page in SettingCenter to enable the extension.image.png

Note
  • Only a workspace administrator can enable an extension on the Extension page in SettingCenter.

  • For more information about extensions, see Overview.

  • The preceding figure shows workspace-level extensions. For more information, see supported extension point events.

Features

Operation Center allows your local services to receive messages when events related to the following extension points are generated. In addition, you can register a local program as a DataWorks extension and use the extension to receive messages related to extension point events. The extension can process extension point events based on your custom logic and send the check result to the platform by calling the UpdateWorkbenchEventResult operation. This helps achieve process control in DataWorks. The following table describes the extension point events that are supported by Operation Center.

Event name

Event content

Node change event

  • Pre-event for node undeployment

  • Pre-event for node freezing

  • Pre-event for node unfreezing

Note

The nodes refer to the auto triggered nodes that are displayed on the Cycle Task page of Operation Center in the production environment.

Data backfill event

  • Event of backfilling data for the current node

  • Event of backfilling data for the current node and its descendant nodes at a time if the current node has a small number of descendant nodes

  • Event of backfilling data for the current node and its descendant nodes at a time if the current node has a large number of descendant nodes

  • Event of backfilling data for multiple selected nodes at a time

Note

The preceding nodes refer to the auto triggered nodes that are listed on the Cycle Task page of Operation Center in the production environment. If you perform the preceding operations on the nodes in the production environment, the registered extensions check the triggered events. If you perform the preceding operations on the nodes in the development environment or freeze or unfreeze node instances on the Cycle Instance page, the extensions do not check the triggered events.

Supported extension point events

Freeze or unfreeze a node in Operation Center

The following figure shows how to trigger and view a check on an event that is generated when you freeze a node.冻结扩展点

Undeploy a node in Operation Center下线节点扩展点

Backfill data for a node in Operation Center补数据扩展点

References