+ Choose the action(s) to take when the rule matches an anomaly. +
++ Choose the action(s) to take when the rule matches an anomaly. +
++ Choose the action(s) to take when the rule matches an anomaly. +
+
+ Rules instruct anomaly detectors to change their behavior based on domain-specific knowledge that you provide. When you create a rule, you can specify conditions, scope, and actions. When the conditions of a rule are satisfied, its actions are triggered.
+
+ Changes to rules take effect for new results only. +
++ To apply these changes to existing results you must clone and rerun the job. Note rerunning the job may take some time and should only be done once you have completed all your changes to the rules for this job. +
+
+ Rules instruct anomaly detectors to change their behavior based on domain-specific knowledge that you provide. When you create a rule, you can specify conditions, scope, and actions. When the conditions of a rule are satisfied, its actions are triggered.
+
+ Changes to rules take effect for new results only. +
++ To apply these changes to existing results you must clone and rerun the job. Note rerunning the job may take some time and should only be done once you have completed all your changes to the rules for this job. +
+
+ Rules instruct anomaly detectors to change their behavior based on domain-specific knowledge that you provide. When you create a rule, you can specify conditions, scope, and actions. When the conditions of a rule are satisfied, its actions are triggered.
+
+ Changes to rules take effect for new results only. +
++ To apply these changes to existing results you must clone and rerun the job. Note rerunning the job may take some time and should only be done once you have completed all your changes to the rules for this job. +
++ Are you sure you want to delete this rule? +
+