After governance items are configured, Data Asset Governance automatically detects issues across your tenant and surfaces them in the To-Do List. This page shows you how to find, prioritize, and act on those issues.
Prerequisites
Before you begin, make sure that:
-
Governance items are configured. See Configure governance items.
Supported data sources and regions
Data Asset Governance handles governance issues for MaxCompute, E-MapReduce (EMR), and Hologres data sources only. To see which governance items apply to each data source type, check the Range column on each tab of the Knowledge page.
Hologres requirements:
-
Collect Hologres metadata in Data Map before using Hologres in Data Asset Governance. See Metadata collection.
-
Hologres data sources are supported only in: China (Beijing), China (Shanghai), China (Hangzhou), and China (Shenzhen).
Permissions
Access to governance issues depends on your role.
| Perspective | Who can view |
|---|---|
| Global — all workspaces in your tenant | Alibaba Cloud account owner; RAM user with AliyunDataWorksfullAccess attached; tenant administrator; tenant-level data governance administrator |
| Workspace — workspaces where you are an administrator | All roles listed under Global, plus: workspace administrator; workspace-level data governance administrator |
| Individual — issues owned by your account | All users |
Regular users can view governance issues only from the Individual perspective.
How health scores relate to governance issues
Governance issues are detected based on the governance items you configure for checking data within the current account. The health score is calculated from those governance items using a built-in assessment model. More issues means a lower health score, which results in a lower rating grade. Handle issues promptly to maintain a healthy score.
For details, see Quantitative assessment: health scores.
View and act on governance issues
Step 1: Go to the To-Do List page
-
Log on to the DataWorks console. In the top navigation bar, select your region.
-
In the left-side navigation pane, choose Data Governance > Data Asset Governance, then click Go to Data Asset Governance.
-
In the left-side navigation pane, choose Overview > Workbench.
-
In the top navigation bar, click Global, Workspace, or Individual to select a perspective.
-
In the To-Do List section, review the count of To-Be-Governed Issues and Assets to Be Governed.
-
Click View More to open the To-Do List page.
You can also navigate directly by choosing Overview > To-Do List in the left-side navigation pane.
Step 2: Drill down to specific issues
The To-Do List page is organized into five interconnected areas. Select items from left to right to narrow your focus.
| Area | What it shows | How to use it |
|---|---|---|
| 1 — Perspective | Switch between Global, Workspace, and Individual views | Select the perspective that matches your role |
| 2 — Governance dimension | Workspace ranking list and issue counts across five dimensions: R&D, Storage, Computing, Quality, and Security | Select a dimension to populate Area 3 |
| 3 — Optimization object | Ranking list of objects with the most issues in the selected dimension — tasks, tables, or Data Service API | Select an object type to populate Area 4 |
| 4 — Issues | Ranking list of specific issues for the selected object type | Select an issue category to populate Area 5 |
| 5 — Issue list | Full list of individual issues with filters and actions | Filter, search, and act on issues |
In Area 5, filter the issue list by workspace, data source type, table owner, operation status, or tag. Search by asset name or ID.
Step 3: Handle each issue
For each issue in the list, choose the action that fits the situation:
| Action | When to use | How to trigger |
|---|---|---|
| Add to whitelist | The issue is a known exception that does not need to be fixed | In the Actions column, choose More > Add to Whitelist. Select multiple issues to bulk-add them. Manage whitelisted issues on the Whitelist page. See Add invalid governance issues to a whitelist. |
| Create plan | The table or task is obsolete and needs to be gracefully decommissioned | In the Actions column, click Create Plan. See Graceful undeployment. |
| Change lifecycle | The node has a lifecycle that needs to be adjusted | In the Actions column, click Change Lifecycle. After you change the lifecycle of the node, the node is executed based on the specified lifecycle. Applies to Storage dimension issues only. |
Table 360: For a panoramic view of a table, click Table 360 in the Actions column to see basic information, governance issues, and task execution details on one page.
Change lifecycle — additional notes:
-
Applies only to governance issues in the Storage dimension.
-
After you change the lifecycle, the system deletes data outside the specified lifecycle every day.
-
For non-partitioned tables, the entire table is deleted if it falls outside the lifecycle.
-
The lifecycle starts from the time the data in the table was last modified.
-
To handle governance issues related to tables, you may need to modify the lifecycles of the tables. Operations supported vary by governance dimension. Follow the instructions in the DataWorks console.
Tags — additional notes:
-
Tags shown in the issue list are offline snapshots and cannot be modified directly.
-
After you add or modify a tag on the Tag Management page, changes take effect the next day. See Manage tags.
What's next
After handling governance issues, choose Overview > Workbench in the left-side navigation pane to view the updated governance results.