negordyh
08/21/2026, 4:40 AMjob_name, so we can manage each tenant/game through job-based filters?kapa.ai
08/21/2026, 4:40 AMjob_name [Collect jobs info from orchestrator; Elementary 0.14.0 release]. If job metadata is collected, you can filter the lineage graph by job and view job details within the node info [Where can I see my job info?].
To enable this with Airflow and dbt Core, you must pass the job metadata explicitly (either via environment variables or dbt --vars), as Airflow does not populate all fields out-of-the-box [Collect jobs info from orchestrator]:
dbt run --vars '{"orchestrator": "airflow", "job_name": "tenant_a_load"}'
Dashboard / Report-Wide Grouping for Multi-Tenancy No, the Elementary OSS dashboard as a whole is not designed to manage or partition multi-tenant runs by `job_name`:
1. Sidebar Navigation & Grouping: The OSS report organizes and separates models in the sidebar by dbt project name, not by job_name or run parameters [multi-tenant discussion; Parameterized model discussion].
2. Metadata Overwrites: In Elementary OSS, metadata tables (like dbt_models, dbt_tests, and dbt_sources) are fully reloaded on each run. If you run the same models for multiple tenants writing to the same Elementary schema, the metadata reflects only the latest run [Parameterized model discussion].
3. Data Storage: Raw run data is stored in dbt_invocations and grouped in the job_run_results view [Where can I see my job info?], where you can query invocations by job_name directly in your warehouse, but this does not create isolated tenant views in the standalone HTML report.
Summary While you can filter by job_name inside the lineage view, using job_name as a global tenant filter/partition across the entire OSS dashboard is not supported. đ 0 button đ 0 button âšī¸ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.