You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/alerts/alerts-troubleshoot-metric.md
+81-1Lines changed: 81 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Common issues with Azure Monitor metric alerts and possible solutio
4
4
author: harelbr
5
5
ms.author: harelbr
6
6
ms.topic: troubleshooting
7
-
ms.date: 2/10/2022
7
+
ms.date: 2/15/2022
8
8
---
9
9
# Troubleshooting problems in Azure Monitor metric alerts
10
10
@@ -301,6 +301,86 @@ Consider one of the following options:
301
301
* If your data has weekly seasonality, but not enough history is available for the metric, the calculated thresholds can result in having broad upper and lower bounds. For example, the calculation can treat weekdays and weekends in the same way, and build wide borders that don't always fit the data. This should resolve itself once enough metric history is available, at which point the correct seasonality will be detected and the calculated thresholds will update accordingly.
302
302
303
303
304
+
## When configuring an alert rule's condition, why is Dynamic threshold disabled?
305
+
While dynamic thresholds are supported for the vast majority of metrics, there are some metrics that can't use dynamic thresholds.
306
+
307
+
The table below lists the metrics that aren't supported by dynamic thresholds.
- For general troubleshooting information about alerts and notifications, see [Troubleshooting problems in Azure Monitor alerts](alerts-troubleshoot.md).
0 commit comments