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/monitor.html.markdown
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -318,6 +318,7 @@ The following arguments are supported:
318
318
-`slo_id` - (Optional) Identifier of the SLO definition for the monitor. This is only applicable & required for Slo `monitor_type`.
319
319
-`queries` - (Required) All queries from the monitor.
320
320
-`trigger_conditions` - (Required if not using `triggers`) Defines the conditions of when to send notifications. NOTE: `trigger_conditions` supplants the `triggers` argument.
321
+
-`resolution_window` - The resolution window that the recovery condition must be met in each evaluation that happens within this entire duration before the alert is recovered (resolved). If not specified, the time range of your trigger will be used.
321
322
-`triggers` - (Deprecated) Defines the conditions of when to send notifications.
322
323
-`notifications` - (Optional) The notifications the monitor will send when the respective trigger condition is met.
323
324
-`group_notifications` - (Optional) Whether or not to group notifications for individual items that meet the trigger condition. Defaults to true.
@@ -406,7 +407,7 @@ Here is a summary of arguments for each condition type (fields which are not mar
406
407
-`resolution` (Required)
407
408
-`threshold`
408
409
-`threshold_type`
409
-
-`resolution_window` : resolution_window overrides the default resolution window which is time_range
0 commit comments