Warehouse lineage
How data moves from each source system through staging into the main schemas, into dna, and out to consumers. Click a schema to see its own lineage and tables.
Line thickness: number of objects linkedSolid: loaded by an Airflow DAG, a view definition or a confirmed sourceDashed: written by analysts' tools, inputs not declared
Schema
| Type | Rows, 16 days | Freshness | Loaded by |
|---|
Airflow DAGs
Every active DAG, its schedule in East Africa Time, and how its runs went over the last 7 days.
| DAG | Schedule (EAT) | Status | Last run started | Last success | Next run | Runs 7 d | Failed 7 d | Avg run |
|---|
Data quality
The Elementary report: every dbt check, source freshness and anomaly monitor, with seven days of history. Trace opens the latest copy with a link that lasts five minutes, so no AWS sign-in is needed.
Latest checks
What it covers
- Tables
- nexus contacts and accounts (pilot)
- Checks
- Keys, required fields, allowed values, relationships
- Monitors
- Volume, freshness and schema changes
- Refreshed
- 07:00, 11:00, 15:00, 19:00 EAT
- Alerts
- Teams alerts channel, prod runs only
dbt docs
The dbt documentation site: every dbt model and source with its columns, descriptions, owner, checks, code and lineage graph.
Project
Where it runs
- DAG
- EL_NEXUS_DBT_PILOT
- Builds into
- nexus_dbt (prod), nexus_dbt_dev (dev)
- Reads
- nexus, read only
- Report files
- s3://prod-analytics-burn-s3/DBT/