Numerical Range

This check looks at every individual value in a numeric column and confirms it falls within an expected range.

It only applies to numeric column types (integer, float, decimal, and similar).

When to use it

A business expects every value in the age column of a users table to fall between 18 and 100. A daily range check flags any row outside this range — for example, a negative age or an unrealistic value like 999 — as a failing row.

What's configurable

• Schedule — fixed recurring, or Manual (requires Full Table Scan if Manual).

• Scan Method — Full Table Scan (whole table each run) or Incremental Scan (only newly arrived rows, based on a timestamp column or filter expression).

• Threshold — a Numeric Range: a minimum and/or maximum. This defines what counts as a failing row — any row whose value falls outside this range. At least one bound is required; bounds are inclusive.

• Tolerance (optional) — how many, or what percentage of, failing rows are allowed before an incident is raised. If you don't set one, even a single failing row triggers an incident.

Worked example — zero tolerance

• Asset: users table, column age

• Scan Method: Full Table Scan

• Schedule: Daily

• Threshold: Numeric Range — min 18, max 65

• Tolerance: not set

Resulting rules:

• "A row fails when the value in age is below 18 or above 65."

• "An incident will be created when any row fails."

Worked example — with tolerance

Same configuration as above, but with a tolerance of 5 failing rows allowed (Absolute tolerance, value 5).

Resulting rule: "An incident will be created when more than 5 rows fail."

Notes

• Changing the schedule or scan method later is a destructive change (it creates a new monitor version). Adjusting only the threshold or tolerance value is not.