Migrated from Github: https://github.com/stolostron/backlog/issues/25604

Value

Search User should know the state of Search at any point of time. If there is a issue we have to get to the search CR status.

Acceptance Criteria

• Check status of all search deployment pods.
• Provide Good status when search is running fine (GraphQL Query responds good for simple query)
• Update the error and the cause if there is a problem with Search runtime (Check if pods are running or make that as communication error)

TODO: Split in 2 stories. (1) Pod status.(https://issues.redhat.com/browse/ACM-2005) (2) Monitor service with running query. (3) expose metric.

Definition of Done for Engineering Story Owner (Checklist)

Development Complete

•  Code is complete.
•  Functionality is working.
•  Any required downstream Docker file changes are made.

Tests Automated

•  Unit/function tests have been automated and incorporated into build.
•  100% automated unit/function test coverage for new or changed APIs.

Secure Design

•  Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

•  Create an informative documentation issue using the Customer Portal_doc_issue template, and ensure doc acceptance criteria is met. Link the development issue to the doc issue.
•  Provide input to the QE team, and ensure QE acceptance criteria (established between story owner and QE focal) is met.

Support Readiness

•  The must-gather script has been updated.