About monitoring coverage

When you open the Monitoring Overview page, a summary of the data quality coverage of your data sources is shown. This provides insight into which data sources might require additional Data Quality Jobs to increase coverage, either through quick monitoring or individual table-level jobs.

When you open a data source on the Monitoring Overview page, a summary of the monitoring coverage of its schemas is shown. In addition to the coverage percentage, the table below the data source metadata shows which schemas have jobs, active monitors, and breaking monitors. These insights help you determine which schemas need additional monitoring coverage.

Example The following example shows the monitoring coverage across 12 schemas in the USERDB Snowflake data source. While 5 schemas have jobs that have run against their tables, 7 do not. For schemas without monitoring, you can click to add quick monitoring to the schema. You might also consider adding additional monitoring to schemas with more tables than jobs, such as AUX, as this imbalance might indicate inadequate coverage.

When you open a schema on the Monitoring Overview page, a summary of its monitoring coverage and details about its active jobs are shown. This helps you determine whether the most important tables in your schema have adequate monitoring or if you need to add additional monitoring to increase coverage.

Example The following example shows that the PUBLIC schema of the USERDB Snowflake data source has a 98% coverage. This level of coverage might be adequate, as 548 jobs have run against the various tables of the PUBLIC schema. However, you can click Add quick monitoring to ensure all tables have coverage.