Merge pull request #99 from flashcatcloud/tmp-1

webhook retry

Author: alick-liming

flashduty/en/1. On-call/8. Integrations/8.5 Webhooks/8.5.1 Alert webhook.md

@@ -152,11 +152,14 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \
 
 1. **Is there a response timeout for the service?**
 
-   - The service must respond within 1 second, after which the response is considered failed
+   - Services must respond within 2 second, responses after 2 second are considered failed
 
 2. **Will failed pushes continue to be pushed?**
 
-   - Currently, Flashduty pushes only once, though retry mechanisms may be introduced in the future. Retries may also occur due to middleware timeouts, so implement idempotent processing
+  For specific network errors, retries will be attempted up to a maximum of 2 times:
+    - context deadline exceeded (excluding cases involving "awaiting headers")
+    - i/o timeout
+    - eof
 
 3. **How is push order guaranteed?**
 

flashduty/en/1. On-call/8. Integrations/8.5 Webhooks/8.5.2 Incident webhook.md

@@ -192,11 +192,14 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \
 
 1. **Is there a response timeout for the service?**
 
-   - Services must respond within 1 second, responses after 1 second are considered failed
+   - Services must respond within 2 second, responses after 2 second are considered failed
 
 2. **Will failed pushes continue to be pushed?**
 
-   - Currently, Flashduty pushes only once, though retry mechanisms may be introduced in the future. Retries may also occur due to middleware timeouts, so implement idempotent processing
+  For specific network errors, retries will be attempted up to a maximum of 2 times:
+    - context deadline exceeded (excluding cases involving "awaiting headers")
+    - i/o timeout
+    - eof
 
 3. **How is push order guaranteed?**
 

flashduty/zh/1. On-call/5. 集成引导/8.5 Webhooks/8.5.1 告警 webhook.md

@@ -152,11 +152,14 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \
 
 1. **服务是否有响应超时时间？**
 
-   - 服务需要在 1 秒内返回响应，超过 1 秒则认为响应失败
+   - 服务需要在 2 秒内返回响应，超过 2 秒则认为响应失败
 
 2. **推送失败后是否会持续推送？**
 
-   - 目前 Flashduty 最多推送一次，未来可能会引入重试机制，也可能因为中间链路超时导致重试，您需要做好幂等处理
+  针对特定的网络错误，会进行重试，最多重试2次:
+    - context deadline exceeded (排除 awaiting headers)
+    - i/o timeout
+    - eof
 
 3. **如何保证推送顺序？**
 

flashduty/zh/1. On-call/5. 集成引导/8.5 Webhooks/8.5.2 故障 webhook.md

@@ -193,11 +193,14 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \
 
 1. **服务是否有响应超时时间？**
 
-   - 服务需要在 1 秒内返回响应，超过 1 秒则认为响应失败
+   - 服务需要在 2 秒内返回响应，超过 2 秒则认为响应失败
 
 2. **推送失败后是否会持续推送？**
 
-   - 目前 Flashduty 最多推送一次，未来可能会引入重试机制，也可能因为中间链路超时导致重试，您需要做好幂等处理
+  针对特定的网络错误，会进行重试，最多重试2次:
+    - context deadline exceeded (排除 awaiting headers)
+    - i/o timeout
+    - eof
 
 3. **如何保证推送顺序？**