Skip to content

Commit d1912b2

Browse files
authored
Merge pull request #159199 from yanivlavi/addmovedidlsa
Added troubleshooting for moved resources
2 parents 667d64e + 13c82ce commit d1912b2

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,10 @@ A common issue is that you think that the alert didn't fire the actions because
4343

4444
![Suppress alerts](media/alerts-troubleshoot-log/LogAlertSuppress.png)
4545

46+
### Alert scope resource has been moved, renamed, or deleted
47+
48+
When you author an alert rule, Log Analytics creates a permission snapshot for your user ID. This snapshot is saved in the rule and contains the rule scope resource Azure Resource Manager ID. If the rule scope resource moves, gets renamed, or deleted, all log alert rules referring to that resource will break. Alert rules will need to be recreated using the new Azure Resource Manager ID to work.
49+
4650
### Metric measurement alert rule with splitting using the legacy Log Analytics API
4751

4852
[Metric measurement](alerts-unified-log.md#calculation-of-measure-based-on-a-numeric-column-such-as-cpu-counter-value) is a type of log alert that is based on summarized time series results. These rules allow grouping by columns to [split alerts](alerts-unified-log.md#split-by-alert-dimensions). If you're using the legacy Log Analytics API, splitting won't work as expected. Choosing the grouping in the legacy API isn't supported.

0 commit comments

Comments
 (0)