elastic/kibana

[Response Ops][Reporting] Use `p-retry` to retry report

Open

#245,437 建立於 2025年12月5日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)TypeScript (19,065 star) (8,021 fork)batch import
Feature:Reporting:FrameworkTeam:ResponseOpsgood first issuequick-win

描述

We added retries within the reporting task to handle retries for scheduled reporting in this PR: https://github.com/elastic/kibana/pull/229998

We should consider switching to using the p-retry library to avoid bugs with custom code.

貢獻者指南

技術棧
typescriptnodejs
領域
backend
議題類型
refactor
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Node.js async/awaitp retry libraryKibana reporting module
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Review the existing retry logic in the reporting task, which was added in PR https://github.com/elastic/kibana/pull/229998. Understand how p retry works by reading its documentation. Then, replace the custom retry code with p retry, ensuring that retry behavior (backoff, count) is preserved. Test the change to verify that scheduled reports are retried correctly. Check the comments on this issue for any additional guidance from maintainers.