Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logical CCS Names: Dynamically reference additional cluster information #108738

Open
simianhacker opened this issue May 16, 2024 · 4 comments
Open
Labels
>enhancement :Search Foundations/CCS Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch

Comments

@simianhacker
Copy link
Member

simianhacker commented May 16, 2024

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.

image

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

@simianhacker simianhacker added >enhancement needs:triage Requires assignment of a team area label labels May 16, 2024
@simianhacker simianhacker changed the title [CCS] Dynamically reference additional cluster information Logical CCS Names: Dynamically reference additional cluster information May 16, 2024
@pgomulka pgomulka added the :Search/Search Search-related issues that do not fall into other categories label May 17, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Search Meta label for search team label May 17, 2024
@elasticsearchmachine
Copy link
Collaborator

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

@elasticsearchmachine elasticsearchmachine removed the needs:triage Requires assignment of a team area label label May 17, 2024
@javanna javanna added :Search Foundations/Search Catch all for Search Foundations and removed :Search/Search Search-related issues that do not fall into other categories labels Jul 17, 2024
@elasticsearchmachine elasticsearchmachine added Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch and removed Team:Search Meta label for search team labels Jul 17, 2024
@elasticsearchmachine
Copy link
Collaborator

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

@javanna javanna added :Search Foundations/CCS and removed :Search Foundations/Search Catch all for Search Foundations labels Jul 17, 2024
@uric
Copy link

uric commented Aug 19, 2024

@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.

@jasonrhodes
Copy link
Member

@uric thank you, this sounds promising! We'll follow along.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement :Search Foundations/CCS Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch
Projects
None yet
Development

No branches or pull requests

6 participants