-
Notifications
You must be signed in to change notification settings - Fork 146
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
Extend test description with anomaly_score and training_stddev #1493
Comments
Hi @adrianoesch ! Just curious, if this issue is still relevant - how would you utilise these values for immediate action on alerts? |
hi @haritamar and thanks for getting back. i would react with more urgency to an anomaly with z-score >5 than one that barely makes it over the threshold. also, anomaly thresholds can be quite fiddly and we're still trying to figure out what good thresholds are for some tests. having the z-score with the alerts therefore would make it easier to get a better feeling of what good thresholds might be when flagging alerts as true or false positives. then, the standard deviation is more of a supplementary peace of information that ties the other values together. it makes the other values easier to deduce but in general less valuable than the z-score. |
Thanks for the explanation @adrianoesch
|
|
Is your feature request related to a problem? Please describe.
We often get alerts in slack with minimal context. I would like to extend the test description with more information, so we can act faster on alerts.
Describe the solution you'd like
I would like to add the
anomaly_score
andtraining_stddev
in the test description string here. Since these strings are the same for column, table and dimension tests, I would create a separate macro named sth likeanomaly_reference_description
that can be called in all three description macros.Would you be willing to contribute this feature?
If this sounds promising to you, I'm happy to contribute a PR.
The text was updated successfully, but these errors were encountered: