elastic/kibana

[telemetry] fetcher.validateConnectivity should wait for core ES service

Offen

#171.888 geöffnet am 23.11.2023

 (1 Kommentar) (1 Reaktion) (0 zugewiesene Personen)TypeScript (8.021 Forks)batch import
Feature:TelemetryTeam:Coreenhancementgood first issue

Repository-Metriken

Stars
 (19.065 Sterne)
PR-Merge-Metriken
 (PR-Metriken ausstehend)

Beschreibung

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)

Contributor Guide