[telemetry] fetcher.validateConnectivity should wait for core ES service · elastic/kibana#171888

(1 评论) (1 反应) (0 负责人)TypeScript (19,065 star) (8,021 fork)batch import

Feature:TelemetryTeam:Coreenhancementgood first issue

描述

Initial discussion here: https://github.com/elastic/kibana/pull/171713#pullrequestreview-1743923611

I wonder if we'd like to leverage the ES core service status as well (prob before setting up the timer, or merged). This way, if Kibana starts when ES is not available, it doesn't need to wait 12H to trigger the next connectivity check.

The telemetry connection check

https://github.com/elastic/kibana/blob/0b91e6db9b5fadcf2146ae8c174d3a3b49383239/src/plugins/telemetry/server/fetcher.ts#L98-L113

requires to fetch the telemetry config SO from the SO index. Therefore, the observable chain should ideally depend on the core ES service's status to only fetch when ES is up (and to try as soon as ES is up)

贡献者指南

技术栈: typescriptnodejselasticsearch
领域: backendobservability
议题类型: feature
难度: 3
预计时间: half day
活动状态: stale
清晰度: clear
前置要求: RxJSKibana plugin developmentElasticsearch core serviceTypeScript
新手友好度: 55
研究方向: Investigate the telemetry fetcher in src/plugins/telemetry/server/fetcher.ts, especially the existing connectivity check logic. Review the referenced PR discussion at https://github.com/elastic/kibana/pull/171713 for details on the desired dependency on the core ES service status. Look into how the core ES service exposes its status and how other plugins handle waiting for ES readiness. The change likely involves adding a filter or delay in the observable chain to wait for the ES core service to be available before setting up the connectivity timer.