The dbt-native data observability solution for data & analytics engineers. Monitor your data pipelines in minutes. Available as self-hosted or cloud service with premium features.
Describe the bug
The row_count metric stopped being collected when we bumped our dbt version to 1.8 (previously on 1.7). Also, elementary does not inform that this is happening. I had to check in the test_result_rows table to find that there are no entries from the day of the bumping onwards.
To Reproduce
Run dbt 1.8
Specify a elementary.volume_anomalies check based on a timestamp column
Specify seasonality day_of_week
Test results log as 98 failures for some weird reason, metrics are not present in the test_result_rows table
Expected behavior
I expect the behavior of elementary to be the same across dbt versions. So my volume_anomalies check should continue as normal.
Environment (please complete the following information):
Elementary CLI (edr) version: 0.13.0
Elementary dbt package version: 0.13.0
dbt version 1.8.6
Data warehouse: BigQuery
We are running the elementary jobs in Cloud Run, using python:3.12.4-slim-bullseye image
Would you be willing to contribute a fix for this issue?
I am happy to contribute but I have no clue what may be wrong!
Describe the bug The row_count metric stopped being collected when we bumped our dbt version to 1.8 (previously on 1.7). Also, elementary does not inform that this is happening. I had to check in the
test_result_rowstable to find that there are no entries from the day of the bumping onwards.To Reproduce
elementary.volume_anomaliescheck based on a timestamp columnday_of_weektest_result_rowstableExpected behavior I expect the behavior of elementary to be the same across dbt versions. So my
volume_anomaliescheck should continue as normal.Environment (please complete the following information):
python:3.12.4-slim-bullseyeimageWould you be willing to contribute a fix for this issue? I am happy to contribute but I have no clue what may be wrong!