Skip to content

Commit dbf49e7

Browse files
Court72AbbyMSFT
andauthored
Apply suggestions from PR review
Co-authored-by: AbbyMSFT <[email protected]>
1 parent e3fb5c3 commit dbf49e7

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

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

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -136,9 +136,14 @@ If you can see a fired alert in the portal, but its configured action did not tr
136136
1. **Are you calling Slack or Microsoft Teams?**
137137
Each of these endpoints expects a specific JSON format. Follow [these instructions](../alerts/action-groups-logic-app.md) to configure a logic app action instead.
138138

139-
1. **Did your webhook became unresponsive or returned errors?**
140-
141-
Our timeout period for a webhook response is 10 seconds. The webhook call will be retried up to two additional times when the following HTTP status codes are returned: 408, 429, 503, 504, or when the HTTP endpoint does not respond. The first retry happens after 10 seconds. The second and final retry happens after 100 seconds. If the second retry fails, the endpoint will not be called again for 15 minutes for any action group.
139+
1. **Did your webhook become unresponsive or return errors?**
140+
141+
The webhook response timeout period is 10 seconds. When the HTTP endpoint does not respond or when the following HTTP status codes are returned, the webhook call is retried up to two times:
142+
- 408
143+
- 429
144+
- 503
145+
- 504
146+
One retry occurs after 10 seconds and another retry occurs after 100 seconds. If the second retry fails, the endpoint is not called again for 15 minutes for any action group.
142147

143148
## Action or notification happened more than once
144149

0 commit comments

Comments
 (0)