@kapa.ai I see that within our Unmonitored dbt tables, you include source tables, which will never have a dbt test given they are not materialized as models in our repository. Is there a way to exclude them?

Based on the knowledge sources, there isn't a direct built-in way to exclude specific source tables from the "Unmonitored tables" view in Elementary. However, there are a few workarounds you can consider: 1. Add a tag to mark them intentionally unmonitored: You can add a tag (e.g.,

no_monitor

or

unmonitored

) to those sources in your

dbt_project.yml

or source YAML files, and then filter the dashboard by that tag to focus only on what matters to you. [Slack forum discussion] 2. Disable the source entirely: If a source should be fully ignored by Elementary, you can set

enabled: false

on it. When a source is disabled, it is removed from the dbt graph, and Elementary will ignore it since it reads schemas from the dbt graph. You can even make this conditional using a dbt variable:- name: source_B enabled: "{{ var('include_source_b', false) }}" database: database_b schema: schema_b tables: - name: table_b_1[Slack forum discussion] 3. Use

--exclude

when running dbt: You can use dbt selectors to exclude specific sources from runs, which means Elementary won't collect results for them. [Slack forum discussion] It's worth noting that there is an open GitHub issue (#794) requesting the ability to exclude models/sources from Elementary reports based on tags, so this is a known limitation the team is aware of. [Slack forum discussion] 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.