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
@@ -213,8 +220,8 @@ The following arguments are supported:
213
220
-`Logs`: A logs query monitor.
214
221
-`Metrics`: A metrics query monitor.
215
222
-`queries` - (Required) All queries from the monitor.
216
-
-`trigger_conditions` - (Required if not using `triggers`) Defines the conditions of when to send notifications. NOTE: `trigger_conditions` supplants the `triggers` argument.
217
-
-`triggers` - (Deprecated) Defines the conditions of when to send notifications.
223
+
-`trigger_conditions` - (Beta) (Required if not using `triggers`) Defines the conditions of when to send notifications. NOTE: `trigger_conditions` supplants the `triggers` argument.
224
+
-`triggers` - Defines the conditions of when to send notifications.
218
225
-`notifications` - (Optional) The notifications the monitor will send when the respective trigger condition is met.
219
226
-`group_notifications` - (Optional) Whether or not to group notifications for individual items that meet the trigger condition. Defaults to true.
220
227
@@ -228,7 +235,7 @@ Additional data provided in state:
228
235
-`Normal`
229
236
-`Disabled`
230
237
231
-
## The `trigger_conditions` block
238
+
## The `trigger_conditions` block (Beta)
232
239
A `trigger_conditions` block configures conditions for sending notifications.
233
240
### Example
234
241
```hcl
@@ -337,62 +344,6 @@ and at most 1 missing-data condition:
337
344
-`logs_missing_data_condition`
338
345
-`metrics_missing_data_condition`
339
346
340
-
## The `triggers` block
341
-
The `triggers` block is deprecated. Please use `trigger_conditions` to specify notification conditions.
342
-
343
-
Here's an example logs monitor that uses `triggers` to specify trigger conditions:
0 commit comments