add re_data_anomalies_filtered as var #116
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
closes re-data/re-data#403
How
Add a var for
re_data_anomalies_filtered
that can override the alerts. In this way, you can select fromre_data_anomalies
what anomalies you would like to show in alerts in the UI, and also notify in slack.After this change, the user can create a model (view, ephemeral, table, anything works) on top of
re_data_anomalies
, for example, the viewanomaly_filters
Then set up re_data:re_data_anomalies_filtered: anomaly_filters
in
dbt.project.yml` and that is all.Tried it on my current project by loading
and then set up
re_data:re_data_anomalies_filtered: anomaly_filters
in mydbt_project.yml
whereanomaly_filters
is an ephemeral model on top ofre_data_anomalies
It worked as expected and
re_data_alerts
is now filtered onanomaly_filters