Data Quality & Lineage Monitor · Documentation
How to Use This Demo
Driving Data Quality & Lineage Monitor in the host, the Cloud/OSS inspector, and the operator console — with honest labels.
← Data Quality & Lineage Monitor- 1
Signing in
The ecosystem is gated. Sign in as the owner for full access or as the in-scope viewer for the operator experience. This app is viewer-visible; reviewing thresholds in CONFIGURE is owner-only.
- 2
Reading the monitor
OPERATE opens with pass / warn / fail health tiles, then a rule table: each row shows the entity.field, the dimension and threshold, a 14-day trend sparkline, the latest score, and a status pill. For any warn or fail rule, click Explain for a metered AI-assist root-cause hypothesis. Below the table, the lineage graph lays out entities, events and apps in three columns with labelled edges (writes, emits, rolls up, aggregates).
Owners open CONFIGURE to review the per-rule pass thresholds. The Audit tab carries platform actions, including the seeded dq.failed entry for the degrading rule.
- 3
The Cloud/OSS inspector
Explain is the only metered step. Flip the mode switch and open "Behind the scenes" to see the trace (profile · explain), the mode badge, and the cost. Cloud runs `claude-haiku-4-5` cost-capped and fail-closed; OSS is recorded at $0. Rules, scores, rollups and the lineage graph are deterministic and free. Instrumentation is inspector-only.