I have several tests failing every day, with alert_suppression_interval set to 24 hours, so we get an alert every day. i dont have enough time in the day to address the failures every day. is there a way to suppress specific tests or models from alerting the slack channel easily without updating the dbt/elementary config code? like a way to input the model or test that i want to manually supress somewhere lets say an aws secret that passes to edr monitor? i am on OSS, not the paid elementary version. what is the recommended workflow for a situation like this?

Suppressing Specific Tests/Models Without Code Changes (Elementary OSS) The knowledge sources do not describe a built-in mechanism to dynamically suppress specific tests or models via an external input like an AWS Secret — that's not a supported native feature in Elementary OSS. Here's an honest breakdown of your options: Option 1: Increase the suppression interval (simplest, code change required) If you can't address failures daily, simply raise the suppression interval for the noisy models/tests in your

.yml

files:

models:
  - name: my_model_name
    config:
      meta:
        alert_suppression_interval: 168  # 1 week

Or globally via CLI:

edr monitor --suppression-interval 168

A week (168 hours) is a reasonable interval for upstream issues you can't fix immediately — community members use this exact value for that scenario. [Alerts configuration] [CLI options] Option 2: Use CLI filters to exclude specific tags/models (no .yml meta change, but still a config change) You can tag models you want to suppress and then run

edr monitor

with a filter that excludes them. However, this still requires tagging in your dbt project config. [Alerts CLI flags] Option 3: Dynamic suppression via an external input (your AWS Secret idea) The knowledge sources do not describe a native way to pass a list of suppressed models/tests via an environment variable, AWS Secret, or similar external input to

edr monitor

. There is no

--suppress-models

or equivalent flag. A workaround you could engineer yourself (not documented by Elementary): • Store a list of models/tags to suppress in an AWS Secret or environment variable • In your Airflow DAG, read that value and dynamically construct the

edr monitor --filters

command to only alert on models NOT in that list This is a custom solution and not something Elementary OSS supports out of the box. Recommended Workflow for Your Situation Based on community discussions, the recommended approach for "failing tests I can't fix right now" is: 1. Set a longer

alert_suppression_interval

(e.g., 168 hours) on the specific models/tests causing noise — this is a one-time code change per model. 2. Set test severity to

warn

instead of

error

if the failures are also breaking your pipeline runs — this keeps the test active without causing DAG failures. 3. Accept that the Elementary report/dashboard will still show the failures — suppression only affects Slack notifications, not the report. [Suppression docs] A proper "acknowledge/snooze" UI mechanism has been raised as a feature request by the community but is not yet implemented in OSS. [Feature request] 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.