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/platform/alerts-troubleshoot.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ If you can see a fired alert in the Azure portal, but did not receive the email
29
29
30
30
1.**Is the type of action "Email Azure Resource Manager Role"?**
31
31
32
-
This action only looks at Azure Resource Manager role assignments that are at the subscription scope, and of type *User*. Make sure that you have assigned the Resource Manager role at the subscription level, and not at the resource level or resource group level.
32
+
This action only looks at Azure Resource Manager role assignments that are at the subscription scope, and of type *User*. Make sure that you have assigned the role at the subscription level, and not at the resource level or resource group level.
33
33
34
34
1.**Are your email server and mailbox accepting external emails?**
35
35
@@ -120,11 +120,13 @@ If you can see a fired alert in the portal, but its configured action did not tr
120
120
121
121
1.**Did a webhook not trigger?**
122
122
123
-
1.**Have the source IP addresses been blocked?**
124
-
Whitelist the [IP addresses](action-groups.md#action-specific-information) that the webhook is called from.
123
+
1.**Have the source IP addresses been blocked?**
124
+
125
+
Whitelist the [IP addresses](action-groups.md#action-specific-information) that the webhook is called from.
126
+
127
+
1.**Does your webhook endpoint work correctly?**
125
128
126
-
1.**Does your webhook endpoint work correctly?**
127
-
Verify the webhook endpoint you have configured is correct and the endpoint is working correctly. Check your webhook logs or instrument its code so you could investigate (for example, log the incoming payload).
129
+
Verify the webhook endpoint you have configured is correct and the endpoint is working correctly. Check your webhook logs or instrument its code so you could investigate (for example, log the incoming payload).
128
130
129
131
1.**Are you calling Slack or Microsoft Teams?**
130
132
Each of these endpoints expects a specific JSON format. Follow [these instructions](action-groups-logic-app.md) to configure a logic app action instead.
@@ -176,7 +178,9 @@ If you have received the alert, but believe some of its fields are missing or in
176
178
177
179
If you can see a fired alert in the portal, but a related action rule did not work as expected, follow these steps:
178
180
179
-
1.**Is the action rule enabled?** Check the action rule status column to verify that the related action role is enabled.
181
+
1.**Is the action rule enabled?**
182
+
183
+
Check the action rule status column to verify that the related action role is enabled.
0 commit comments