Skip to content

Commit 2d8614f

Browse files
authored
Merge pull request #188038 from yanivlavi/patch-19
Fixed the create flow docs
2 parents f8ba26e + 7d74dcc commit 2d8614f

File tree

1 file changed

+0
-11
lines changed

1 file changed

+0
-11
lines changed

articles/azure-monitor/alerts/alerts-log.md

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -44,17 +44,6 @@ You can also [create log alert rules using Azure Resource Manager templates](../
4444

4545
:::image type="content" source="media/alerts-log/alerts-create-new-alert-rule.png" alt-text="Create new alert rule.":::
4646

47-
1. The **Create alert rule** wizard opens to the **Select a signal** page of the **Condition** tab, with the scope already defined based on the resource you selected.
48-
49-
:::image type="content" source="media/alerts-log/alerts-create-new-rule-select-signal.png" alt-text="Select signal.":::
50-
51-
1. Click on the **Custom log search** signal.
52-
1. Write a query to identify the conditions for triggering alerts. You can use the [alert query examples topic](../logs/queries.md) to understand what you can discover or [get started on writing your own query](../logs/log-analytics-tutorial.md). Also, [learn how to create optimized alert queries](alerts-log-query.md).
53-
1. Click **Run** to confirm that the query correctly identifies the data you want to alert on.
54-
55-
:::image type="content" source="media/alerts-log/alerts-logs-query-results.png" alt-text="Query results.":::
56-
57-
1. Once you have successfully finished writing your query, click **Continue Editing Alert**.
5847
1. The **Condition** tab opens, populated with your log query.
5948

6049
:::image type="content" source="media/alerts-log/alerts-logs-conditions-tab.png" alt-text="Conditions Tab.":::

0 commit comments

Comments
 (0)