hey team, did something change with the "--disable-samples=TRUE" argument for edr monitor with the new update? we suddenly get Test results sample again in the alerts, which do not comply with our GDPR 😕 is there a new solution how to exclude them?

Hey @Julia Masche, TY for raising that up! I am checking, and will update once I'll have an answer 🙂

Hey @Idan Shavit thank you so much 🙌🏻 one more question: I also noticed that the alerts are being sent out twice. Are you aware of that already?

Hey @Julia Masche, we are not aware of a duplicate alerts issue 🤔 Can you tell me on which kind of alerts this is happening to you? (tests/models/source freshness/all) Can I ask if you see the duplicate alerts on the table

alerts_v2

?

hey @Idan Shavit, for now only for tests 🙂 And yes, I can also see duplicate alerts on the table

alerts_v2

, e.g.

Interesting 🤔 Can I ask you to check if you have duplicate rows on your

dbt_tests

table as well? It will help me understand where should I research 🙏

I couldn't find duplicates there, no 🙂

Thanks for the info! One more question (hopefully the last) - Do you run multiple

edr monitor

commands at the same time?

sure no worries. we do indeed 🙂 but for different departments, so there is no intersection in terms of tests or models.

Got it thanks! So I think that this is the issue 🙂 The way our alerts are working is: 1. We populate the alerts_v2 table from all of the artifacts elementary package has collected 2. We filter the relevant alerts according to the

filters

argument 3. We send the alerts Because you are running

edr monitor

at the same time, both of the runs have the same state where the new alerts do not exist, so both create them - which it is what creates the duplication. If you'll run the

edr monitor

commands one after the other, it will stop creating the duplicate rows at the alerts_v2 table 🙂

ok understood 🙂 thank you @Idan Shavit for the help and explanation 🙌