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
NOTE: Monitor folders are considered a different resource from Library content folders. See [sumologic_monitor_folder][2] for more details.
@@ -480,7 +520,8 @@ A `trigger_conditions` block contains one or more subblocks of the following typ
480
520
-`metrics_missing_data_condition`
481
521
-`slo_sli_condition`
482
522
-`slo_burn_rate_condition`
483
-
-`log_anomaly_condition`
523
+
-`logs_anomaly_condition`
524
+
-`metrics_anomaly_condition`
484
525
485
526
Subblocks should be limited to at most 1 missing data condition and at most 1 static / outlier condition.
486
527
@@ -571,14 +612,21 @@ Here is a summary of arguments for each condition type (fields which are not mar
571
612
-`burn_rate_threshold` (Required): The burn rate percentage threshold.
572
613
-`time_range` (Required): The relative time range for the burn rate percentage evaluation. Accepted format: Optional `-` sign followed by `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `30m`, `-12h`.
573
614
574
-
#### log_anomaly_condition
615
+
#### logs_anomaly_condition
575
616
-`field`: The name of the field that the trigger condition will alert on. The trigger could compare the value of specified field with the threshold. If field is not specified, monitor would default to result count instead.
576
617
-`anomaly_detector_type`: The type of anomaly model that will be used for evaluating this monitor. Possible values are: `Cluster`.
577
618
-`critical`
578
619
-`sensitivity`: The triggering sensitivity of the anomaly model used for this monitor.
579
620
-`min_anomaly_count` (Required) : The minimum number of anomalies required to exist in the current time range for the condition to trigger.
580
621
-`time_range` (Required) : The relative time range for anomaly evaluation. Accepted format: Optional `-` sign followed by `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `30m`, `-12h`.
581
622
623
+
#### metrics_anomaly_condition
624
+
-`anomaly_detector_type`: The type of anomaly model that will be used for evaluating this monitor. Possible values are: `Cluster`.
625
+
-`critical`
626
+
-`sensitivity`: The triggering sensitivity of the anomaly model used for this monitor.
627
+
-`min_anomaly_count` (Required) : The minimum number of anomalies required to exist in the current time range for the condition to trigger.
628
+
-`time_range` (Required) : The relative time range for anomaly evaluation. Accepted format: Optional `-` sign followed by `<number>` followed by a `<time_unit>` character: `s` for seconds, `m` for minutes, `h` for hours, `d` for days. Examples: `30m`, `-12h`.
629
+
582
630
## The `triggers` block
583
631
The `triggers` block is deprecated. Please use `trigger_conditions` to specify notification conditions.
0 commit comments