Open simianhacker opened 4 months ago
Pinging @elastic/es-search (Team:Search)
Pinging @elastic/es-search-foundations (Team:Search Foundations)
@naj-h this sounds very similar to what we're aiming for with "symlinks" in serverless cross-project search (CPS). @simianhacker there's a CPS offsite this week to hash out the above concept, after which we'll be able to share more details and see if it can be applied to this. The concepts the team is discussing this week are also applicable to Stateful Elasticsearch.
@uric thank you, this sounds promising! We'll follow along.
Description
In the SLO product, we have a "federated" feature we just released where SRE's setup SLO definitions on a remote cluster (via Kibana) and then we query the SLO indices via CCS.
Part of the requirements was having a way to identify which SLOs (on a Overview) cluster are "Remote SLOs" and linking back to the "Remote Kibana" for the details page, edit page, or a link to Discover to view the source data for RCA. To solve this, we are "hard coding" the "Remote Kibana URL" into an ingest pipeline when the SLO is created (or updated) which adds this to the SLO summary document.
While this works and accomplishes our goals, it's fragile due to the fact that if the SRE or Admin ever changes the Kibana URL, they would need to reset the hard coded field in the ingest pipelines for each SLO definition.
Feature Request
CC: @kimchy @uric