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
Support for hourly, weekly, monthly bucket size in anomaly tests #439
Support for hourly, weekly, monthly bucket size in anomaly tests #439
Comments
Hi @rloredo! Thanks for opening this issue, makes perfect sense. |
Thanks again @rloredo, let me know what do you think about this: Here's a short background on our tests - My suggestion is to break down the change to pieces. Here's a description on what's needed to support this -
As the anomaly scores query is shared between all the tests and has a complex logic, I think it's better the team makes the required changes to support the different buckets on that one. |
Hi, @Maayan-s! thank you for your fast response. It looks clearer now :) For the bucket_size thing, I think it's good to change the name... I think we can use this as inspiration. Note that they also use lookback_periods, trend_periods, and test_periods. I guess that days_back should also change to periods_back (or lookback_periods). Let me know what you think and if you want me to take some of this! |
Thanks, @rloredo! What do you think? |
Great, I can give it a try then :) |
So, I did most of the changes in elementary-data/dbt-data-reliability#85
I couldn't make dimension_anomalies work, mainly because of the metrics_anomaly_score view. The #TODO's are marked in the code. This is as far as I can get! Let me know if someone will pick it up and I if you need any clarification :) |
Wow @rloredo, thank you so much! |
In anomaly detection, the default bucket size is 1 day. I couldn't find a way to configure the size of these buckets.
Checking the code here I think that it's not an easy fix, since it also depends on how the data is collected before this query is executed.
I would keep exploring, but perhaps you can guide me on what should be done to be able to do this.
The text was updated successfully, but these errors were encountered: