Getting Started with Observability¶

Observability helps data stewards follow how a container's volume, freshness, and key values change over time. Qualytics records measurements (a row count, the time of the last change, or a value followed by a Metric check) and draws them as charts, so a stalled load or a drifting number is visible at a glance.

Why this matters¶

Important data can change without an obvious warning. A source stops receiving rows, a delivery arrives late, or a business number shifts after a process change. Observability keeps the history of those signals:

• Volume: the row count of each tracked table or file, once a day and whenever a Scan or Profile counts it.
• Freshness: when each tracked container last changed, and how stale it was at each measurement.
• Metric values: the number a Metric check follows, recorded on every Scan that evaluates it.

The charts show the measurements. Alerts come from checks: a Volumetric, Freshness, or Metric check raises an anomaly when a Scan evaluates it and the value is outside its limits. With the AI options on, Qualytics also creates Volumetric and Freshness checks from the history.

How Observability is organized¶

The Observability tab sits on three surfaces:

• Datastore scope. Open a Source Datastore and click the Observability tab to see every tracked container and Metric check in the datastore.
• Container scope. Open a table or file and click the Observability tab to see only that container.
• Explore scope. From the global Explore section, the Observability page lists them across every datastore you have access to.

At the top of each surface, two tabs group the charts:

• Measures. One card per container, with its volume and freshness measurements and the Volumetric and Freshness checks that use them.
• Metrics. One card per Metric check, with the values it recorded.

Next Steps¶