Erica Bertan
06/23/2026, 5:46 PMdbt test -s 'tag:non-blocking-test tag:elementary' in one task, then edr monitor in a subsequent task to send Slack alerts.
We're seeing duplicate notifications: Airflow's failure callback fires when the dbt test task fails, and edr monitor sends its own Slack alert for the same failure. To avoid the duplication, we're trying to understand exactly what edr monitor picks up from the test results table.
Does edr monitor alert on all dbt test failures stored in the Elementary results table (including generic dbt tests), or only on tests tagged with tag:elementary?kapa.ai
06/23/2026, 5:46 PMedr monitor will alert on all failed dbt tests that Elementary has recorded, not just tests tagged with tag:elementary, unless you explicitly filter it.
Key points from the docs and community threads:
• Elementary records the results of all dbt tests (native, dbt-utils, custom, Elementary, etc.) into elementary_test_results via the elementary.handle_tests_results on‑run‑end hook.[elementary_test_results; All dbt tests]
• edr monitor then reads from those results and sends alerts for failures according to your configuration; by default it is not limited to a specific tag.[CLI commands]
• To restrict alerts to only certain tests (e.g., those tagged elementary), you must use the --filters flag, for example:edr monitor --filters tags:elementarywhich will only send alerts for tests/models whose aggregated tags include elementary.[Alerts CLI flags; Tag filtering example ]
So in your current setup:
• dbt test -s 'tag:non-blocking-test tag:elementary' controls which tests run, but
• edr monitor (without --filters) will alert on any failures from that run, regardless of tag.
If you want Elementary alerts only for the tag:elementary tests (and let Airflow/dbt handle others), run:
edr monitor --filters tags:elementary 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.