Create a monitor

Create a monitor through the three-step wizard, and change one you already have.

You create monitors from the Monitors tab. The wizard splits into three steps, grouped by how permanent each decision is: what the monitor watches, how it evaluates, and how it is described.

Step 1: Asset and monitor type

Pick the asset you want to add the monitor to. You can use the filters to narrow down the selections.

The asset and the monitor type are fixed once the monitor exists. To watch a different table, or run a different check, create a new monitor.

Step 2: Configuration

This is where you set how the monitor runs and what counts as a failure. The fields you see depend on the monitor type, drawn from the same set each time:

• Schedule, how often the monitor runs, or Manual if you trigger it yourself.

• Detection method, how Decube measures the asset.

• Threshold, the boundary that separates a passing value from a failing one.

• Tolerance, how many failing rows you accept before the run fails. Row-level checks use this.

Every field is explained once in Building Blocks, and each monitor type page shows the fields for that type with a worked example.

Step 3: Properties

Name the monitor, describe what it protects, and set the properties your team filters and reports on:

• Data quality dimension, which determines where this monitor contributes to your DQ Scorecard.

• Custom attributes, your own tags and key-value pairs (severity, domain, owning team). Alert rules read these, so attributes you set here decide who gets notified.

Attributes are defined for your organisation under Org settings > Custom attributes, with Monitors as the applicable object.

After you save

The monitor becomes Active and runs at its next scheduled time. Open it from the Monitors tab to see run history, the cases it raised, and the alert rules that currently match it.

Change an existing monitor

Open the monitor and use Monitor actions > Edit. You land on the step that holds the field you want, and the other steps stay as they are.

Some changes alter what the monitor measures, so its past runs no longer compare against the new configuration. Decube warns you at the point of the change and creates a new monitor version, keeping earlier runs against the version that produced them.

Changing the same field across many monitors? Use bulk update instead of editing them one at a time.