Logical CCS Names: Dynamically reference additional cluster information

[simianhacker]

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

• Basic solution: Have a way to set and lookup the Kibana URL via the remote cluster definition so we can have a single source of truth for creating dynamic linking to the "Remote Kibana" instance
• Deluxe solution: Everything in the basic solution for linking PLUS have a way for us to execute API requests on the "Remote Kibana" instance via CCS (or some kind of remote execution scheme). This would allow us to query APIs like alerting along with creating and managing SLOs on the remote cluster.

CC: @kimchy @uric

[elasticsearchmachine]

Pinging @elastic/es-search (Team:Search)