Lorenzo Fini
04/09/2026, 1:54 PMkapa.ai
04/09/2026, 1:54 PMedr monitor to the most recent invocation: Key Limitation: No Invocation Filter for edr monitor edr monitor does not support invocation-based filtering. This is explicitly confirmed by Elementary support staff:
> "`edr monitor` does not have an invocation filter, but can be filtered by tags (-fl tags:elementary, --select was deprecated)."
[send-report/monitor Slack]
Note: The --select last_invocation option exists for edr report / edr send-report, but not for edr monitor. Recommended Workarounds 1. Run edr monitor after every dbt execution (recommended) Since Elementary marks alerts as "sent" after each edr monitor run, running it immediately after each dbt invocation ensures you only get alerts for that run's results. This is the approach the Elementary team recommends:
dbt build --select <your_models>
edr monitor --slack-token <your_token> --slack-channel-name <your_channel>
[false alarms Slack] 2. Use --days-back 0 to limit the time window This restricts alerts to only today's results:
edr monitor --days-back 0 --slack-token <your_token> --slack-channel-name <your_channel>
[days-back tip] 3. Use tag-based filters If your dbt runs use tags, you can scope alerts to specific runs:
edr monitor --filters tags:<your_tag> --slack-token <your_token> --slack-channel-name <your_channel>
[alerts configuration] In summary, there is no direct equivalent of --select last_invocation for edr monitor. The most reliable approach is to run edr monitor immediately after each dbt invocation. đ 0 button đ 0 button âšī¸ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.Lorenzo Fini
04/09/2026, 1:56 PMkapa.ai
04/09/2026, 1:57 PM