This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Filter out historical detectors on monitor creation page #229
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Issue #, if available:
Description of changes:
Historical detectors are a new concept in the AD plugin that allow for creating and running the RCF and threshold models and generating anomaly results on historical/past data, rather than just real-time, streaming data. Regarding the data model, historical detectors differ by having an additional
detectionDateRangefield, which describes the specified data time range for the detector to run.Note that historical detectors cannot be configured with monitors and generate alerts, since there is no real-time aspect of them. Because of this, historical detectors need to be filtered out on the monitor creation page. This PR addresses that.
Screenshot of the fix:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.