Skip to content

Commit 36306e5

Browse files
committed
Alerts resource and signal pickers
1 parent cfa0beb commit 36306e5

File tree

2 files changed

+6
-8
lines changed

2 files changed

+6
-8
lines changed

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

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -30,23 +30,20 @@ Then you define these elements for the resulting alert actions by using:
3030

3131
1. On the **Select a resource** pane, set the scope for your alert rule. You can filter by **subscription**, **resource type**, or **resource location**.
3232

33-
The **Available signal types** for your selected resources are at the bottom right of the pane.
34-
3533
> [!NOTE]
3634
> If you select a Log analytics workspace resource, keep in mind that if the workspace receives telemetry from resources in more than one subscription, alerts are sent about those resources from different subscriptions.
3735
3836
:::image type="content" source="media/alerts-create-new-alert-rule/alerts-select-resource.png" alt-text="Screenshot that shows the select resource pane for creating a new alert rule.":::
3937

40-
1. Select **Include all future resources** to include any future resources added to the selected scope.
41-
1. Select **Done**.
38+
1. Select **Apply**.
4239
1. Select **Next: Condition** at the bottom of the page.
43-
1. On the **Select a signal** pane, filter the list of signals by using the signal type and monitor service:
40+
1. On the **Select a signal** pane, you can search for the signal name or you can filter the list of signals by:
4441
- **Signal type**: The [type of alert rule](alerts-overview.md#types-of-alerts) you're creating.
45-
- **Monitor service**: The service sending the signal. This list is pre-populated based on the type of alert rule you selected.
42+
- **Signal source**: The service sending the signal. The list is pre-populated based on the type of alert rule you selected.
4643

4744
This table describes the services available for each type of alert rule:
4845

49-
|Signal type |Monitor service |Description |
46+
|Signal type |Signal source |Description |
5047
|---------|---------|---------|
5148
|Metrics|Platform |For metric signals, the monitor service is the metric namespace. "Platform" means the metrics are provided by the resource provider, namely, Azure.|
5249
| |Azure.ApplicationInsights|Customer-reported metrics, sent by the Application Insights SDK. |
@@ -60,7 +57,8 @@ Then you define these elements for the resulting alert actions by using:
6057
|Resource health|Resource health|The service that provides the resource-level health status. |
6158
|Service health|Service health|The service that provides the subscription-level health status. |
6259

63-
1. Select the **Signal name**, and follow the steps in the following tab that corresponds to the type of alert you're creating.
60+
1. Select the **Signal name** and **Apply**.
61+
1. Follow the steps in the tab that corresponds to the type of alert you're creating.
6462

6563
### [Metric alert](#tab/metric)
6664

-59.3 KB
Loading

0 commit comments

Comments
 (0)