doc fix: add azurerm_monitor_scheduled_query_rules_log and `azurerm…

…_monitor_scheduled_query_rules_alert` missed properties (#19837) Co-authored-by: jackofallops <11830746+jackofallops@users.noreply.github.com>
hashicorp · Jan 3, 2023 · b46e424 · b46e424
1 parent 3a86043
commit b46e424
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 1 deletion.
diff --git a/website/docs/d/monitor_scheduled_query_rules_alert.html.markdown b/website/docs/d/monitor_scheduled_query_rules_alert.html.markdown
@@ -39,6 +39,7 @@ output "query_rule_id" {
 * `enabled` - Whether this scheduled query rule is enabled.
 * `frequency` - Frequency at which rule condition should be evaluated.
 * `query` - Log search query.
+* `query_type` - The type of query results.
 * `time_window` - Time window for which data needs to be fetched for query.
 * `severity` - Severity of the alert.
 * `throttling` - Time for which alerts should be throttled or suppressed.

diff --git a/website/docs/d/monitor_scheduled_query_rules_log.html.markdown b/website/docs/d/monitor_scheduled_query_rules_log.html.markdown
@@ -32,6 +32,7 @@ output "query_rule_id" {
 
 * `id` - The ID of the scheduled query rule.
 * `location` - Specifies the Azure Region where the resource should exist.
+* `authorized_resource_ids` - A list of IDs of Resources referred into query.
 * `criteria` - A `criteria` block as defined below.
 * `data_source_id` - The resource URI over which log search query is to be run.
 * `description` - The description of the scheduled query rule.

diff --git a/website/docs/r/monitor_scheduled_query_rules_alert.html.markdown b/website/docs/r/monitor_scheduled_query_rules_alert.html.markdown
@@ -112,13 +112,14 @@ The following arguments are supported:
 * `frequency` - (Required) Frequency (in minutes) at which rule condition should be evaluated.  Values must be between 5 and 1440 (inclusive).
 * `query` - (Required) Log search query.
 * `time_window` - (Required) Time window for which data needs to be fetched for query (must be greater than or equal to `frequency`).  Values must be between 5 and 2880 (inclusive).
-* `trigger` - (Required) The condition that results in the alert rule being run.
+* `trigger` - (Required) A `trigger` block as defined below.
 * `action` - (Required) An `action` block as defined below.
 * `authorized_resource_ids` - (Optional) List of Resource IDs referred into query.
 * `auto_mitigation_enabled` - (Optional) Should the alerts in this Metric Alert be auto resolved? Defaults to `false`.
 -> **NOTE** `auto_mitigation_enabled` and `throttling` are mutually exclusive and cannot both be set.
 * `description` - (Optional) The description of the scheduled query rule.
 * `enabled` - (Optional) Whether this scheduled query rule is enabled.  Default is `true`.
+* `query_type` - (Optional) The type of query results. Possible values are `ResultCount` and `Number`. Default is `ResultCount`.
 * `severity` - (Optional) Severity of the alert. Possible values include: 0, 1, 2, 3, or 4.
 * `throttling` - (Optional) Time (in minutes) for which Alerts should be throttled or suppressed.  Values must be between 0 and 10000 (inclusive).
 * `tags` - (Optional) A mapping of tags to assign to the resource.

diff --git a/website/docs/r/monitor_scheduled_query_rules_log.html.markdown b/website/docs/r/monitor_scheduled_query_rules_log.html.markdown
@@ -91,6 +91,7 @@ The following arguments are supported:
 * `location` - (Required) Specifies the Azure Region where the resource should exist. Changing this forces a new resource to be created.
 * `criteria` - (Required) A `criteria` block as defined below.
 * `data_source_id` - (Required) The resource URI over which log search query is to be run.
+* `authorized_resource_ids` - (Optional) A list of IDs of Resources referred into query.
 * `description` - (Optional) The description of the scheduled query rule.
 * `enabled` - (Optional) Whether this scheduled query rule is enabled.  Default is `true`.
 * `tags` - (Optional) A mapping of tags to assign to the resource.