Feature Overview

This issue proposes an investigation into the feasibility and implementation of integrating Red Hat Advanced Cluster Management (ACM) Search as a data source within the Perses project (perses.dev). This integration would allow Perses dashboards to leverage the rich, searchable data available within ACM, providing a unified view of cluster management data for users.

https://perses.dev/perses/docs/plugins/creation/ 

Goals

This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature

• Determine the technical feasibility of connecting Perses to ACM Search as a data source.
• Identify the necessary APIs or mechanisms within ACM Search to extract relevant data.
• Understand the data structure and querying capabilities of ACM Search to map them effectively to Perses' data model.
• Assess the potential benefits and use cases for users who would consume ACM Search data through Perses dashboards.
• Provide recommendations and an estimated effort for a full implementation, if deemed feasible.
• Collaborate and work with Red Hat Observability team to open RFEs if any technical gaps exist in Perses that block a ACM Search-based plugin.

Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

(Optional) Use Cases

This Section:

• Main success scenarios - high-level user stories
• Alternate flow/scenarios - high-level user stories
• ...

Questions to answer

• ...

Out of Scope

• …

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Assumptions

• ...

Customer Considerations

• ...

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have a doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?