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.
[Response Ops][Reporting] Use `p-retry` to retry report · elastic/kibana#245437 | Good First Issue