Skip to content

Commit 761afac

Browse files
committed
alert rule
1 parent d97308b commit 761afac

1 file changed

Lines changed: 1 addition & 2 deletions

File tree

articles/azure-monitor/alerts/alerts-create-log-alert-rule.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -103,8 +103,7 @@ Alerts triggered by these alert rules contain a payload that uses the [common al
103103
|Frequency of evaluation|How often the query is run. Can be set anywhere from one minute to one day (24 hours).|
104104
105105
> [!NOTE]
106-
> There are some limitations to using a <a name="frequency">one minute</a> alert rule frequency. When you set the alert rule frequency to one minute, an internal manipulation is performed to optimize the query. This manipulation can cause the query to fail if it contains unsupported operations. The following are the most common reasons a query are not supported:
107-
106+
> There are some limitations to using a <a name="frequency">one minute</a> alert rule frequency. When you set the alert rule frequency to one minute, an internal manipulation is performed to optimize the query. This manipulation can cause the query to fail if it contains unsupported operations. The following are the most common reasons a query are not supported:
108107
> * The query contains the **search**, **union** or **take** (limit) operations
109108
> * The query contains the **ingestion_time()** function
110109
> * The query uses the **adx** pattern

0 commit comments

Comments
 (0)