Change Monitor
Know Which Metrics Move When A Model Changes
Suspended Change Echo Panels. A dbt model, field type, or Join change creates the First Layer Echo; panels farther away show affected Metrics, Dashboards, Reports, then Business Teams — deeper dependencies hang farther back.
First Layer Echo · Modelfct_billing_eventsdbt model change: customer_id renamed to account_id; join type shifted
MetricsActive Customers, ARPC, Net Revenue Retention3 metric contracts reference this column
DashboardsFinance Weekly, Board Deck, Growth Pulse2 dashboards render an affected metric
ReportsQ3 Board Pack, Weekly Ops CSVexported reports still point at the old grain
Business TeamsFinance, Growth, Executive3 teams see a number that may shift
Change scanned — Follow An Echo to see each depth this rename reaches.
- Scan Model Change — detect a schema or logic change on merge
- Follow An Echo — trace impact depth by depth
- Open Affected Metric — see exactly which contract is exposed
- Assign Review Owner — route to the right metric owner
- Approve Impact Scope — sign off that the blast radius is known
A Correct Query Can Still Produce The Wrong Metric.
Illuminate The True Grain Of Every Metric.
GrainLux is the AI Semantic Data Reliability Layer between your warehouse and every model, metric, and dashboard built on top of it — grain-aware, metric-native, explainable, and deterministic.