Volumetric Anomaly Reporting¶

How the Volumetric check reports a volume outside its limits: what the Shape Anomaly tells you, how to read its numbers for each comparison, and why there is nothing to report per row.

Anomaly Messages¶

Volumetric emits a Shape Anomaly only, one per failed evaluation. The message names the container, the volume the Scan observed, and the limit it crossed:

What failed	Message
The volume is below the lower limit	`orders received 0 records, fewer than the expected minimum of 1`
The volume is above the upper limit	`orders received 62400 records, more than the expected maximum of 45000`

When both limits are set, the message reports whichever one was crossed. Numbers are shown without thousands separators. An average or a percentage-based limit can carry decimals, and they are rounded only as far as the two numbers still read in the right order.

What the Numbers Mean¶

The two numbers in the message are always row counts, even when the limits you configured are changes or percentages. The check turns your limits into expected row counts before comparing:

Comparison	Observed value in the message	Expected limit in the message
Absolute Value, `1` day	The row count the Scan read	Your Min or Max
Absolute Value, `N` days	The average daily row count across the period	Your Min or Max
Absolute Change	The row count the Scan read	The count one Measurement Period earlier, plus your Min or Max
Percentage Change	The row count the Scan read	The earlier count, increased or decreased by your Min or Max percentage

To recover the earlier count, subtract your Min or Max from the expected limit for Absolute Change. For Percentage Change, divide the expected limit by one plus your Min or Max as a decimal: an expected maximum of 150 with a Max of 50% means an earlier count of 150 / 1.5 = 100. For example, an Absolute Change check with Min 1 on a table that held 25000 rows yesterday and still holds 25000 today reports received 25000 records, fewer than the expected minimum of 25001.

When No Anomaly Is Created¶

The check reports nothing, and is recorded as Not Asserted for that Scan, when:

The container's row count could not be read at Scan time.
The measurement history is missing a day the comparison needs. See The History the Check Needs.

A day without a Scan never produces an anomaly, even when the Observability chart shows the volume outside the limits.

Source Records Behavior¶

Volumetric does not evaluate rows, so the anomaly carries no source records. The evidence is the container's row-count history, available on its Observability chart. From the check form, the View Volumetric chart button opens it directly.

Custom Anomaly Description¶

The form does not offer Custom Anomaly Description for this rule. The option replaces the message on Record Anomalies, and Volumetric has no field to select and emits a Shape Anomaly only, so the message is always the fixed one above.