Enable asset monitoring

How to create, view, and manage monitors for your data assets from the Config module.

The Config module is where you create and manage all data quality monitors. It has two tabs: All Monitors, which shows every monitor across your connected sources, and Create, where you set up new monitors.

Before creating your first monitor, make sure your data source is connected and your alert channels are configured in Config Settings.

Grouped-By monitors are set up within each monitor type's creation flow. Schema Drift and Job Failure monitors are managed directly from the All Monitors tab.


All Monitors tab

The All Monitors tab lists every monitor in your organisation, with its current status, last run time, and scan frequency.

All Monitors tab

To manage an existing monitor, click the ellipsis (︙) at the far right of the monitor row. This opens two options:

View Monitor — opens the monitor configuration form, where you can modify settings, disable the monitor, or delete it.

Monitor configuration form
Delete monitor option

Monitor Info — opens the monitor's history and performance data, with two tabs:

  • History — lists each scan run with its timestamp and result status:

    • Passed — the scan ran and the metric was within the expected range.

    • Failed — the scan ran and the metric fell outside the expected range, triggering an incident.

    • Skipped — the scan ran but could not collect metrics, or the baseline threshold has not yet been established. See sparse data behaviour.

    • Errored — the scan could not run. Contact [email protected] if this persists.

Monitor scan history
  • Performance — shows the monitored metric over time, alongside the confidence interval or threshold bounds.

Monitor performance view

Create tab

Navigate to Config > Create to set up a new monitor. Select the monitor type card that matches what you want to detect.

Monitor type cards in the Create tab

Available monitor types

Monitor type
What it detects
Setup guide

Data that has stopped arriving on its expected schedule

Row-count increments outside the expected range

Column-level anomalies — nulls, uniqueness, ranges, patterns

Business rule violations defined by custom SQL logic

Table structure changes (auto-enabled)

ETL pipeline job execution failures (auto-enabled)

For a full description of each type, see Available Monitor Types.


Getting started

If you're setting up monitoring for the first time:

  1. Start with Freshness and Volume monitors on your most business-critical tables.

  2. Add Field Health monitors on key columns once the table-level monitors are in place.

  3. Use Custom SQL for any validation logic that the built-in tests don't cover.

Schema Drift and Job Failure monitors are enabled automatically when you connect a data source — no setup required.

Last updated