Skip to content

Commit 81ca0a2

Browse files
committed
overview
1 parent 8269025 commit 81ca0a2

File tree

2 files changed

+13
-11
lines changed

2 files changed

+13
-11
lines changed

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

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

7272
:::image type="content" source="media/alerts-log/alerts-create-log-rule-logic.png" alt-text="Screenshot of alert logic section of a new log alert rule.":::
7373

74-
1. (Optional) In the **Advanced options** section, you can specify the number of failures and the alert evaluation period required to trigger an alert. For example, if you set the **Aggregation granularity** to 5 minutes, you can specify that you only want to trigger an alert if there were three failures (15 minutes) in the last hour. This setting is defined by your application business policy.
74+
1. (Optional) In the **Advanced options** section, you can specify the number of failures and the alert evaluation period required to trigger an alert. For example, if you set the **Aggregation granularity** to 5 minutes, you can specify that you only want to trigger an alert if there were three failures (15 minutes) in the last hour. This setting is defined by your application business policy.
7575

76-
Select values for these fields under **Number of violations to trigger the alert**:
76+
Select values for these fields under **Number of violations to trigger the alert**:
7777

78-
|Field |Description |
79-
|---------|---------|
80-
|Number of violations|The number of violations that have to occur to trigger the alert.|
81-
|Evaluation period|The amount of time within which those violations have to occur. |
82-
|Override query time range| Enter a value for this field if the alert evaluation period is different than the query time range.|
78+
|Field |Description |
79+
|---------|---------|
80+
|Number of violations|The number of violations that have to occur to trigger the alert.|
81+
|Evaluation period|The amount of time within which those violations have to occur. |
82+
|Override query time range| Enter a value for this field if the alert evaluation period is different than the query time range.|
8383

84-
:::image type="content" source="media/alerts-log/alerts-rule-preview-advanced-options.png" alt-text="Screenshot of the advanced options section of a new log alert rule.":::
84+
:::image type="content" source="media/alerts-log/alerts-rule-preview-advanced-options.png" alt-text="Screenshot of the advanced options section of a new log alert rule.":::
8585

8686
1. The **Preview** chart shows query evaluations results over time. You can change the chart period or select different time series that resulted from unique alert splitting by dimensions.
8787

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

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,15 +10,17 @@ ms.custom: template-concept
1010

1111
# Types of Azure Monitor alerts
1212

13-
There are four kinds of Azure Monitor alerts:
13+
This article describes the kinds of Azure Monitor alerts you can create, and helps you understand when to use each type of alert.
14+
15+
There are four types of alerts:
1416
- [Metric alerts](#metric-alerts)
1517
- [Log alerts](#log-alerts)
1618
- [Activity log alerts](#activity-log-alerts)
1719
- [Smart detection alerts](#smart-detection-alerts)
1820

1921
## Choosing the right alert type
2022

21-
This table can help you decide when to use each alert type. See the [pricing page](https://azure.microsoft.com/pricing/details/monitor/) for more detailed information about pricing.
23+
This table can help you decide when to use what type of alert. See the [pricing page](https://azure.microsoft.com/pricing/details/monitor/) for more detailed information about pricing.
2224

2325
|Alert Type |When to Use |Pricing Information|
2426
|---------|---------|---------|
@@ -133,7 +135,7 @@ To monitor for the same condition on multiple Azure resources, you can use split
133135
You may also decide not to split when you want a condition applied to multiple resources in the scope. For example, if you want to fire an alert if at least five machines in the resource group scope have CPU usage over 80%.
134136

135137
### Using the API
136-
Manage new rules in your workspaces using the [ScheduledQueryRules](/rest/api/monitor/scheduledqueryrule-2021-08-01/scheduled-query-rules) API.
138+
Manage new rules in your workspaces using the [ScheduledQueryRules](https://docs.microsoft.com/rest/api/monitor/scheduledqueryrule-2021-08-01/scheduled-query-rules) API.
137139

138140
> [!NOTE]
139141
> Log alerts for Log Analytics used to be managed using the legacy [Log Analytics Alert API](api-alerts.md). Learn more about [switching to the current ScheduledQueryRules API](alerts-log-api-switch.md).

0 commit comments

Comments
 (0)