Handle pre-check events-DataWorks(DataWorks)-阿里云帮助中心

After you configure check items, Data Asset Governance detects check events for your account. In the DataWorks governance center, you can view key metrics—such as total checks, issues found, discovery rate, forced blocks, and blocking rate—to help you promptly identify and handle these events. This topic describes how to view and handle check events.

Prerequisite

Check items are configured. For more information, see Configure check items.

Background

Check items run proactively during pre-commit stages, such as task submission, to prevent new governance issues. When a check item finds an issue, it triggers a check event.
The health score is a quantitative assessment of issues found by governance items. It is calculated using a defined model to reflect your account's governance level. For more information about health scores, see Quantitative assessment: health score.
You can view check events from different perspectives: Global, Workspace View, or Individual.

Permissions

To view check events from the Global perspective, you must have one of the following permissions:
- Alibaba Cloud account
- RAM user with the AliyunDataWorksfullAccess permission
- tenant administrator
- tenant-level data governance administrator
To view check events from the Workspace View perspective, you must have one of the following permissions:
- Alibaba Cloud account
- RAM user with the AliyunDataWorksfullAccess permission
- workspace administrator
- tenant administrator
- tenant-level data governance administrator
- workspace-level data governance administrator
Regular users can only view check events from the Individual perspective.

Note

Data Asset Governance supports check events for MaxCompute, E-MapReduce, Hologres, DLF, and StarRocks. To see which data source types apply to each check item, see the Range column on the knowledge base page.

Note

To use a Hologres compute resource in Data Asset Governance, you must first collect its metadata with Data Map. For more information, see Metadata collection.
Data Asset Governance supports Hologres compute resources only in the China (Beijing), China (Shanghai), China (Hangzhou), and China (Shenzhen) regions.

View and handle check events

Go to the Data Asset Governance page.
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose Data Governance > Data Asset Governance. On the page that appears, click Go to Data Asset Governance.
In the left-side navigation pane, choose Governance > Check Event to go to the Check Event page.

View and handle check events.

On the Check Event page, you can use the Global, Individual, or Workspace View perspective to view check event overviews and details for your account, identify blocked check events, and handle blocking issues in a timely manner. The following figure uses the Global perspective as an example to show the Check Event page.

Area	Description
①	In this area, you can select the perspective from which to view check events. Global: View check events across all DataWorks workspaces under the target tenant. Workspace View: View check events for a specific workspace where you are the workspace administrator. In this perspective, you can select the workspace from the Workspaces Managed by Me list. Individual: View check events for which you are the owner. Note For permission requirements for different perspectives, see Permissions.
②	In this area, you can view the overview of check events in the current perspective by using the Total Checks, Issue Detection Times, Issue Detection Rate, Blocking Times, and Forced Blocking Rate metrics, along with the Day-on-day or Month-on-month increase or decrease ratios for each category, so that you can quickly understand the processing trends of check events.
③	In this area, you can use the Distribution by Check Result and Distribution by Check Type pie charts to view an overview of check events broken down by different categories. This helps you quickly understand the distribution of check events across different dimensions within each category.
④	In this area, you can filter check events by category—R&D, Storage, Computing, Quality, and Security—and use the Workspace and Check Status filters to view details of check events that match the specified conditions (such as Check Item Name, Operated By, Occurred At, Check Object Type, and Check Object). Note Pay special attention to check events whose Check Status is Check Failed. These events may block the normal execution of data development workflows. Contact the relevant operators to handle them in a timely manner.

Next step

After check events are handled, you can go to the Governance > Check Event page again to verify whether the check status of the corresponding check items is Check Passed.