Spencer Bonar
10/12/2023, 9:52 PMAlex Alves
10/13/2023, 7:19 AMAlex Alves
10/13/2023, 7:20 AMlocal-dbt-runs channel to send the alerts of these occasional local runs:
Override configuration from dbt project: Sometimes, for example during testing and development, you want all your alerts sent to a single slack channel, without suppression, regardless of how they are configured in the model config block or schema.yml in your dbt project. You can do this by using this flag. Please note that when using this flag without passing a suppression interval parameter, the suppression interval for all the alerts will be overridden by the default value, 0
edr monitor --override-dbt-project-config --slack-token <your_slack_token> --slack-channel-name <slack_channel_to_post_at> --suppression-interval 0Spencer Bonar
10/13/2023, 2:27 PMI am very curious, why you don’t want to be alerted in this case?Sorry, I can do a better job of explaining here! In these instances, in which a user is running a model against a production target and there's a failure, they're already getting that failure message in terminal because they're running locally. So the slack message ends up being superfluous. But again, a pretty infrequent edge case for us, I just figured I'd ask. That said...adding
dbt_user and orchestrator to the alerts model might generally be useful? Just so that when I'm reviewing slack alerts I have that context