Allow override of incremental look-back period

[smitsrr]

This doesn't fail if you don't have the project variable declared, but does allow for changing the incremental look-back period by setting the variable in the project:

vars:
  dbt_snowflake_monitoring_incremental_days: 0

Why:
We want to run the package every 10 minutes and a 7-day look back period is prohibitively expensive (by time and cost). For our use case, we don't care about the potential loss of accuracy due to late-arriving rate data.

[ian-whitestone]

don't think this syntax is valid, need the where.

same thing below.

[smitsrr]

adjusted!!

[ian-whitestone]

Thanks for the PR @smitsrr

I'm good with this behaviour given that the field isn't required.

We want to run the package every 10 minutes

Purely out of curiosity, what's the use case / monitoring you are driving off of this?

[smitsrr]

Thanks for the PR @smitsrr

I'm good with this behaviour given that the field isn't required.

We want to run the package every 10 minutes

Purely out of curiosity, what's the use case / monitoring you are driving off of this?

First, we love the package for having all of the queries enriched and associated with dbt models. Our other source was dbt_artifacts, but that doesn't include all of the queries that are run for an incremental model.
The reason we want to run it so frequently is because it will give us a way to monitor where our daily execution is at, before waiting for the dbt tasks to complete (and on-run-end is executed for dbt artifacts to be written to the db).

[ian-whitestone]

First, we love the package for having all of the queries enriched and associated with dbt models. Our other source was dbt_artifacts, but that doesn't include all of the queries that are run for an incremental model.

got it, thanks for the context @smitsrr !!