Skip to content

Commit f0d5e06

Browse files
Merge pull request #278670 from AbbyMSFT/assorted-fixes
Several unrelated updates
2 parents 5dabb3a + 5e11524 commit f0d5e06

File tree

5 files changed

+8
-6
lines changed

5 files changed

+8
-6
lines changed

articles/azure-monitor/alerts/alerts-dynamic-thresholds.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: AbbyMSFT
55
ms.author: abbyweisberg
66
ms.reviewer: yalavi
77
ms.topic: conceptual
8-
ms.date: 05/28/2023
8+
ms.date: 06/19/2024
99
---
1010

1111
# Create a metric alert with dynamic thresholds

articles/azure-monitor/alerts/alerts-manage-alert-instances.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ You can save up to 10 views of the alerts timeline. The **default** view is the
7878

7979
The **Alert details** page provides more information about the selected alert:
8080

81-
- To change the user response to the alert, select the pencil near **User response**.
81+
- To change the user response to the alert, select the pencil near **User response**. The User response can be **New**, **Acknowledged**, or **Closed**.
8282
- To see the details of the alert, expand the **Additional details** section.
8383
- To see all closed alerts, select the **History** tab.
8484

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Alerts consist of:
4141
- Webhooks.
4242
- Event hubs.
4343
- **Alert conditions**: These conditions are set by the system. When an alert fires, the alert condition is set to **fired**. After the underlying condition that caused the alert to fire clears, the alert condition is set to **resolved**.
44-
- **User response**: The response is set by the user and doesn't change until the user changes it.
44+
- **User response**: The response is set by the user and doesn't change until the user changes it. The User response can be **New**, **Acknowledged**, or **Closed**.
4545
- **Alert processing rules**: You can use alert processing rules to make modifications to triggered alerts as they're being fired. You can use alert processing rules to add or suppress action groups, apply filters, or have the rule processed on a predefined schedule.
4646
## Types of alerts
4747

articles/azure-monitor/alerts/alerts-resource-move.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ description: Background and instructions for how to update alert rules or alert
44
ms.author: abbyweisberg
55
ms.topic: how-to
66
ms.custom: subject-moving-resources
7-
ms.date: 05/28/2023
8-
ms.reviewer: ofmanor
7+
ms.date: 06/19/2024
8+
ms.reviewer: nolavime
99
---
1010

1111
# Update alert rules or alert processing rules when their target resource moves to a different Azure region

articles/azure-monitor/best-practices-alerts.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,16 @@ description: Provides a template for a Well-Architected Framework (WAF) article
44
ms.topic: conceptual
55
author: AbbyMSFT
66
ms.author: abbyweisberg
7-
ms.date: 09/04/2023
7+
ms.date: 06/19/2024
88
ms.reviewer: abbyweisberg
99
---
1010

1111
# Best practices for Azure Monitor alerts
1212
This article provides architectural best practices for Azure Monitor alerts, alert processing rules, and action groups. The guidance is based on the five pillars of architecture excellence described in [Azure Well-Architected Framework](/azure/architecture/framework/).
1313

14+
1415
For more information about alerts and notifications, see [Azure Monitor alerts overview](./alerts/alerts-overview.md).
16+
For more information about alerting at-scale solutions, see [Alerting at-scale](alerts/alerts-overview.md#alerting-at-scale).
1517

1618
## Reliability
1719
In the cloud, we acknowledge that failures happen. Instead of trying to prevent failures altogether, the goal is to minimize the effects of a single failing component. Use the following information to minimize failure of your Azure Monitor alert rule components.

0 commit comments

Comments
 (0)