Metabase
Map every Metabase question, dashboard, and model to the warehouse tables, transformations, and source systems they depend on.
Semantic Layers & BIWhy Metabase matters
Metabase encourages broad access: analysts and business users create saved questions and dashboards using raw SQL or the visual query builder, often without the data team knowing. Dashboards proliferate fast, Metabase models add business logic inside the BI tool, and nobody has a complete picture of the dependencies between Metabase and the warehouse. Upstream changes break dashboards silently.
Typedef surfaces the full inventory of Metabase content that depends on each warehouse table, so upstream teams know the true downstream footprint of their data assets and root cause analysis extends through the BI layer.
What Typedef unlocks
Impact analysis into the BI layer
Before changing an upstream table, see every Metabase question, dashboard, and collection affected, including self-service queries the data team has no visibility into.
Dashboard-to-source tracing
Follow any Metabase metric or saved question back through the warehouse, transformation layer, and source systems across the full platform.
Self-service sprawl visibility
Surface the full inventory of saved questions and dashboards that depend on each warehouse table so teams understand their true downstream footprint.
Question cleanup and migration
Consolidate redundant questions, retire unused dashboards, or migrate BI tools with full visibility into what each question queries and who relies on it.
Related integrations
Make calculated fields, LOD expressions, and data blending logic visible to the rest of the platform for impact analysis.
Surface the modeling layer inside Power BI so impact analysis and lineage do not stop at the BI boundary.
Surface the business logic hidden inside LookML so impact analysis doesn't stop at the BI layer.
See the full picture: what feeds every table and what depends on it across the stack.