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
Currently, the results fetched when triggered from OSD Visualizations are limited to real-time results (see here). Ideally, users have the flexibility to also include historical results to be overlaid to provide more insights to users, particularly if they have large amounts of historical data and historical anomaly results.
Added logic to fetch the latest historical task ID and fetch historical results with that ID can be used to fetch the latest run of historical results for a particular detector - this is already done on the historical analysis tab, and that logic can be reused here. This may also mean adding or updating parameters in the expression function if we want to allow users to specify to include historical or not, and if so, we should handle backward compatibility scenarios gracefully (e.g., default to only real-time if no param is found).
The text was updated successfully, but these errors were encountered:
Currently, the results fetched when triggered from OSD Visualizations are limited to real-time results (see here). Ideally, users have the flexibility to also include historical results to be overlaid to provide more insights to users, particularly if they have large amounts of historical data and historical anomaly results.
Added logic to fetch the latest historical task ID and fetch historical results with that ID can be used to fetch the latest run of historical results for a particular detector - this is already done on the historical analysis tab, and that logic can be reused here. This may also mean adding or updating parameters in the expression function if we want to allow users to specify to include historical or not, and if so, we should handle backward compatibility scenarios gracefully (e.g., default to only real-time if no param is found).
The text was updated successfully, but these errors were encountered: