Skip to content

Introduction to the Time Distribution Size Check

The Time Distribution Size check groups rows into time segments by a date field and asserts that each segment holds a plausible number of records. It can spot a day that arrived short or an hour that arrived twice, even when the overall totals still look right. Pair it with a Freshness check to detect periods that never arrived at all.

This section is the complete guide to the check. The Deep Dive covers the definition, properties, and full evaluation semantics, explains how anomalies are reported, walks through production examples, and collects best practices; the How-tos are step-by-step tutorials for creating, editing, and deleting a check; the API page documents the payload for programmatic use; and the FAQ answers the most frequent questions.

Next Steps

  • How It Works

    The complete reference: definition, field scope, the interval, the count range, what a segment is, filter behavior, and why coverage does not apply.

    How It Works

  • Anomaly Reporting

    The Shape Anomaly the check produces, what the percentage counts, and how the failing segments are reported.

    Anomaly Reporting

  • Examples

    Three production scenarios with sample data, the resulting anomaly message, and the SQL equivalent of what the check evaluates.

    Examples

  • Best Practices

    Guidelines for picking the interval, sizing the range, and handling seasonality.

    Best Practices

  • Permissions

    The team permission each action needs: view, create, edit, archive, restore, and delete.

    Permissions

  • Create a Check

    Step-by-step tutorial for creating a Time Distribution Size check on a date or timestamp field.

    Create a Check

  • Edit a Check

    Step-by-step tutorial for changing the interval or the count range on an existing check.

    Edit a Check

  • Delete a Check

    Step-by-step tutorial for archiving a check and deleting it permanently.

    Delete a Check

  • Troubleshooting

    Common problems with interval choice, sparse segments, seasonality, and aggregate anomaly reporting.

    Troubleshooting

  • API

    Payload shape and field notes for creating a Time Distribution Size check programmatically.

    API

  • FAQ

    Short answers to questions about intervals, the count range, empty segments, and anomaly reporting.

    FAQ