Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All anomaly checks failing after upgrading to 0.16.0 #1671

Closed
henriklaurentz opened this issue Aug 13, 2024 · 2 comments
Closed

All anomaly checks failing after upgrading to 0.16.0 #1671

henriklaurentz opened this issue Aug 13, 2024 · 2 comments
Labels
Bug Something isn't working Triage 👀

Comments

@henriklaurentz
Copy link

henriklaurentz commented Aug 13, 2024

Describe the bug
All our anomaly checks are raising column "metric_type" does not exist in data_monitoring_metrics during dbt test after upgrading to dbt 0.16.0.

To Reproduce
Steps to reproduce the behavior:

1.Apply some "model level" tests

    data_tests:
      - elementary.table_anomalies:
          tags: ["elementary"]
          severity: warn
      - elementary.dimension_anomalies:
          tags: ["elementary"]
          severity: warn
          dimensions:
            - tool
      - elementary.all_columns_anomalies:
          tags: ["elementary"]
          severity: warn

  1. Run dbt test
  2. Receive errors along the lines of:
[2024-08-13, 10:28:03 UTC] {pod_manager.py:447} INFO - [base]   Database Error in test elementary_all_columns_anomalies_slv_events_document_analytics_ (models/silver/events/production/events.yml)
[2024-08-13, 10:28:03 UTC] {pod_manager.py:447} INFO - [base]   column "metric_type" does not exist in data_monitoring_metrics

Expected behavior
That the anomaly tests runs simply successfully, as on former versions.

Screenshots
The columns in data_monitoring_metrics, closest to metric_type being metric_name

image

Environment (please complete the following information):

  • Elementary CLI (edr) version: Irrelevant
  • Elementary dbt package version: 0.16.0
  • dbt version you're using: 1.8.3
  • Data warehouse: Redshift
  • Infrastructure details: "Production" nightly dbt run + dbt test ran from Airflow in k8s pod.

Additional context
To clarify, dbt deps + dbt run -s elementary has been ran before running dbt test on version 0.16.0

Would you be willing to contribute a fix for this issue?
Not sure if that would be the most pragmatic approach :)

@henriklaurentz henriklaurentz added Bug Something isn't working Triage 👀 labels Aug 13, 2024
@haritamar
Copy link
Collaborator

Hi @henriklaurentz !
Can you please clarify if the dbt run -s elementary runs were executed on the same dbt profile as your production environment?
Because this should fix the issue (we indeed added a field to data_monitoring_metrics)

@henriklaurentz
Copy link
Author

Oh my sweet lawd, my apologies, that was very sloppy of me. At least staging is 100%+ upgraded :)

Thanks for the reply and have a nice evening!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Triage 👀
Projects
None yet
Development

No branches or pull requests

3 participants