Hi #C02CTC89LAX! Currently working on spinning up Elementary OSS for our dbt project. We orchestrate using Prefect, the plan is to have the Elementary report sent out at the end of our daily dbt model run/test flows. What is the best way to exclude ad-hoc model runs from the data displayed in the Elementary dashboard? We only want to see dbt run/test results from our daily flow runs.

Hey @Alex Ilyin, Have you tried using tags ? You can set a "daily" tags for your daily models/tests, and filter them on elementary's report. Lmk if this meets your needs

Hi @Daniel Pollak! I’m not sure this solves the issue I’m describing. We’re currently running elementary in both our production as well as our staging/dev environments. Since we also run models ad-hoc in the staging environment, I was trying to find a way to “containerize” the data that elementary sees so it doesn’t get mixed into our daily elementary reports

Can you elaborate more about the usecase ? Not sure I 100% understood it.

So in our use case, we have models running on a daily basis in our staging/development environment. We generate a edr report based on the results from those model runs orchestrated by Prefect. We also test code changes and run models ad-hoc (outside of our daily models runs) in the same staging env. Will Elementary collect data on models runs/tests from those development runs? and will that data show up in the Elementary report? If so, how can that situation be avoided?

Ok, so you want to disable elementary for specific runs. Check this, lmk if this does help

Yep I think that’s exactly what I had in mind! Thank you @Daniel Pollak