Monitoring and discovery

Once pipelines are running, three questions come up every day: what does this data mean, where does it come from, and is everything healthy and affordable? Three apps answer them.

​

Catalog: what is this data?

The Catalog is the searchable index of your data assets. It pulls together your dbt™ documentation, column descriptions, tests, and metadata from connected tools so anyone on the team can find a model and understand it without reading SQL. The quality of the Catalog reflects the quality of your dbt™ docs; teams often use DinoAI to backfill descriptions at scale.

​

Lineage: where does it come from?

Lineage draws the dependency graph of your data: from raw sources, through staging and marts models, out to the dashboards that consume them. Use it to answer impact questions (“what breaks if I change this column?”) and provenance questions (“which source feeds this number?”). Developers also get lineage inside the Code IDE while editing, including column-level lineage on supported integrations.

​

Radar: is it healthy and affordable?

Radar is observability for your data platform:

• Cost management: where your Snowflake or BigQuery spend goes, and which models or queries drive it.
• dbt™ monitoring: run health, failures, and test results over time.
• BI monitoring and team efficiency: how dashboards and the team itself are performing.
• Real-time alerting: get told when something crosses a line, before a stakeholder does.

​

Who uses these

These three apps are fully available to read-only (Business) users, which makes them the natural home for analysts, stakeholders, and anyone who consumes data without writing dbt™ code.

​

Where to go next