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
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -321,7 +321,7 @@ The following arguments are supported:
321
321
-`notifications` - (Optional) The notifications the monitor will send when the respective trigger condition is met.
322
322
-`group_notifications` - (Optional) Whether or not to group notifications for individual items that meet the trigger condition. Defaults to true.
323
323
-`playbook` - (Optional - Beta) Notes such as links and instruction to help you resolve alerts triggered by this monitor. {{Markdown}} supported. It will be enabled only if available for your organization. Please contact your Sumo Logic account team to learn more.
324
-
-`alert_name` - (Optional) The display name when creating alerts. Monitor name will be used if `alert_name` is not provided. All template variables can be used in `alert_name` except `{{AlertName}}` and `{{ResultsJson}}`.
324
+
-`alert_name` - (Optional) The display name when creating alerts. Monitor name will be used if `alert_name` is not provided. All template variables can be used in `alert_name` except `{{AlertName}}`, `{{AlertResponseURL}}` and `{{ResultsJson}}`.
325
325
-`notification_group_fields` - (Optional - Beta) The set of fields to be used to group alerts and notifications for a monitor. The value of this field will be considered only when 'groupNotifications' is true.
326
326
-`obj_permission` - (Optional) `obj_permission` construct represents a Permission Statement associated with this Monitor. A set of `obj_permission` constructs can be specified under a Monitor. An `obj_permission` construct can be used to control permissions Explicitly associated with a Monitor. But, it cannot be used to control permissions Inherited from a Parent / Ancestor. Default FGP would be still set to the Monitor upon creation (e.g. the creating user would have full permission), even if no `obj_permission` construct is specified at a Monitor and the FGP feature is enabled at the account.
327
327
-`subject_type` - (Required) Valid values:
@@ -387,6 +387,8 @@ A `trigger_conditions` block contains one or more subblocks of the following typ
387
387
-`metrics_outlier_condition`
388
388
-`logs_missing_data_condition`
389
389
-`metrics_missing_data_condition`
390
+
-`slo_sli_condition`
391
+
-`slo_burn_rate_condition`
390
392
391
393
Subblocks should be limited to at most 1 missing data condition and at most 1 static / outlier condition.
0 commit comments