You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Security ML team during testing of one of our Anomaly detection job found out that using both time_of_week and time_of_day functions within a single job config is not ideal. This is because time_of_week uses a different time format, modeling time as epoch seconds modulo the number of seconds in a week. To prevent confusion and save time, it’s recommended to add a note advising against this, either at the beginning of the page or within the time_of_week section.
We can add something similar to below:
Since time_of_day and time_of_week use different time formats, we recommend against using them together in a single Anomaly Detection job.
Description
The Security ML team during testing of one of our Anomaly detection job found out that using both
time_of_week
andtime_of_day
functions within a single job config is not ideal. This is becausetime_of_week
uses a different time format, modeling time as epoch seconds modulo the number of seconds in a week. To prevent confusion and save time, it’s recommended to add a note advising against this, either at the beginning of the page or within thetime_of_week
section.We can add something similar to below:
Related Issue:
The text was updated successfully, but these errors were encountered: