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
Copy file name to clipboardExpand all lines: website/docs/r/cse_match_rule.html.markdown
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,9 +49,9 @@ The following arguments are supported:
49
49
+`default` - (Optional) The severity to use in the "constant" case or to fall back to if the field used by "fieldValue"/"fieldValueMapping" is not populated.
50
50
+`field` - (Optional) The field to use in the "fieldValue"/"fieldValueMapping" cases.
51
51
+`mapping` - (Optional) The map of record values to severities to use in the "fieldValueMapping" case
52
-
-`type` - (Required) Must be set to "eq" currently
53
-
-`from` - (Required) The record value to map from
54
-
-`to` - (Required) The severity value to map to
52
+
-`type` - (Required) Must be set to "eq" currently
53
+
-`from` - (Required) The record value to map from
54
+
-`to` - (Required) The severity value to map to
55
55
-`summary_expression` - (Optional) The summary of the generated Signals
56
56
-`tags` - (Required) The tags of the generated Signals
57
57
-`suppression_window_size` - (Optional) For how long to suppress Signal generation, in milliseconds. Must be greater than 0 and less than the global limit of 7 days.
@@ -65,4 +65,4 @@ The following attributes are exported:
65
65
Match Rules can be imported using the field id, e.g.:
66
66
```hcl
67
67
terraform import sumologic_cse_match_rule.match_rule id
0 commit comments