The Quality Dashboard displays key data quality metrics, rule check trends, top issue tables and owners, and rule coverage for your workspace, helping you identify and resolve quality issues efficiently.
Access the quality dashboard
Log on to the DataWorks console. In the target region, click in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Quality.
-
In the left-side navigation pane, click Quality Dashboard.
Usage notes
The Quality Dashboard displays data quality statistics for the current workspace.
-
In the upper-right corner of the dashboard, you can select to view statistics for Today, Yesterday, The Day Before Yesterday, or a custom date range. By default, the dashboard displays real-time statistics for today.
-
Select View Only Data in Production Environment to display statistics for the production environment only.
NoteIf you select this option, check results for development tables are not included in the statistics. Only workspaces in standard mode have separate development and production environments. In basic mode, all data tables are production tables. For more information, see Differences between basic mode and standard mode.
-
You can also view the data quality overview from one of the following perspectives:
-
All: Displays data quality statistics for all engine types in the current workspace.
-
A specific data source ( MaxCompute , E-MapReduce , Hologres , CDH Hive , AnalyticDB for PostgreSQL , AnalyticDB for MySQL , StarRocks , MySQL , and more): Displays statistics for the selected data source.
NoteStatistics for streaming data are not supported.
-
Key data quality metrics
In this section, select Rule or Table on the right to view key data quality metrics by rule or by table.
|
Category |
Metric |
Description |
|
Table |
Number of tables with configured rules |
The number of tables in the workspace with configured data quality rules for the selected date. |
|
Number of tables with quality issues |
The number of tables where at least one check instance completed with a status other than Check Passed on the selected date. This includes threshold violations and system errors. Completed Tables: The number of tables for which a check instance was completed on the selected date. A completed instance can have a status of Passed, a threshold violation, or a system error. |
|
|
Number of tables with strong rule issues |
The number of tables where a strong rule check completed with a status other than Check Passed on the selected date. This includes threshold violations and system errors. Tables That Hit Critical Threshold: The number of tables that violated a strong rule's critical threshold on the selected date. Tables That Hit Warning Threshold: The number of tables that violated a strong rule's warning threshold on the selected date. |
|
|
Number of tables with weak rule issues |
The number of tables where a weak rule check completed with a status other than Check Passed on the selected date. This includes threshold violations and system errors. Tables That Hit Critical Threshold: The number of tables that violated a weak rule's critical threshold on the selected date. Tables That Hit Warning Threshold: The number of tables that violated a weak rule's warning threshold on the selected date. |
|
|
Rule |
Total data quality rules |
The total number of rules created in the current workspace as of the selected date. |
|
Number of rules with issues |
The number of rules with a check instance that completed with a status other than Check Passed on the selected date. This includes threshold violations and system errors. Completed Rules: The number of rules for which a check instance was completed on the selected date. A completed instance can have a status of Passed, a threshold violation, or a system error. |
|
|
Number of strong rules with issues |
The number of strong rules with a check instance that completed with a status other than Check Passed on the selected date. This includes threshold violations and system errors. Rules Based on Which Tables Hit Critical Threshold: The number of rules for which a check instance violated a strong rule's critical threshold on the selected date. Rules Based on Which Tables Hit Warning Threshold: The number of rules for which a check instance violated a strong rule's warning threshold on the selected date. |
|
|
Number of weak rules with issues |
The number of weak rules with a check instance that completed with a status other than Check Passed on the selected date. This includes threshold violations and system errors. Rules Based on Which Tables Hit Critical Threshold: The number of rules for which a check instance violated a weak rule's critical threshold on the selected date. Rules Based on Which Tables Hit Warning Threshold: The number of rules for which a check instance violated a weak rule's warning threshold on the selected date. |
Quality check monitoring
View the trends and distribution of rule check results.
Instance trend analysis

Shows the trend of rule check results. You can view statistics By Day or By Hour. You can also filter the view to show trends for All, Strong rules, or Weak rules.
Instance run status

Shows the distribution of rule check results for the selected date. You can also filter the view to show the status distribution for All, Strong rules, or Weak rules. The run statuses include:
-
Check Passed: The check ran successfully, and its result met the quality threshold.
-
Strong Rule-based Check Instances for Which Critical Threshold Is Exceeded: A strong rule's critical threshold was violated.
-
Strong Rule-based Check Instances for Which Warning Threshold Is Exceeded: A strong rule's warning threshold was violated.
-
Weak Rule-based Check Instances for Which Critical Threshold Is Exceeded: A weak rule's critical threshold was violated.
-
Weak Rule-based Check Instances for Which Warning Threshold Is Exceeded: A weak rule's warning threshold was violated.
-
Check Failed: The check failed to run because the system was unable to obtain the value to be checked.
Top quality issues
Ranks tables by the number of rule issues and displays the Top N Tables with Maximum Number of Quality Issues and owners of tables with quality issues within the selected time range. Click View more in the upper-right corner to go to the Running Records page, where you can review the table's check history, view check details, and resolve any issues.
The owner of a quality rule is the owner of the associated table partition. This owner is typically the user who created the partition filter expression.
Quality configuration analysis
Displays the overall coverage of data quality rules for tables across the following dimensions: Number of tables with configured quality rules-Asset Ratio, No Rules Are Configured-Number of Tables, No Rules Are Enabled-Number of Tables, Configured with Rules with Which No Scheduling Node Is Associated-Number of Tables, and Configured with Rules for Which No Alert Recipient Is Configured-Number of Tables. You can also click View Details in the Actions column to view the rule configuration details for each table. Five summary metric cards appear at the top, including the Asset ratio of tables with configured rules card, which shows the percentage of data tables with quality rules configured. The ranking table below lists details for each table, such as the Number of configured rules, Number of enabled rules, Number of rules associated with scheduling, Subscribed alert objects, and Number of problematic rules in the last 30 days. You can click View Details to view the configuration of a single table. The dimensions are described as follows:
-
No Rules Are Configured: Counts tables that have no configured data quality rules.
NoteCurrently, statistics are calculated only for MaxCompute data sources.
-
No Rules Are Enabled: Counts tables that have configured rules, but none are enabled.
-
Configured with Rules with Which No Scheduling Node Is Associated: Counts tables with configured quality rules that are not associated with a scheduling node. Rules without a scheduling association run only when triggered manually.
-
Configured with Rules for Which No Alert Recipient Is Configured: Counts tables with quality rules that have no alert recipient configured. Without a recipient, no notifications are sent when issues are detected.