Value Statement

Expose metrics from search components will help with debugging and SLOs

Definition of Done for Engineering Story Owner (Checklist)

This is a continuation of the work featured in ACM-3288. We already have metrics for total search request duration but we need to divide this metric based on request type (query type). We should have labels for the following queries:

• Time it takes to build RBAC filter. (latency)
• Search query.
• Autocomplete (suggestions) query.
• Relationships query.
• Count query (saved searches cards).

Development Complete

• The 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 the
  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](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  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) are met.

Support Readiness

• [ ] The must-gather script has been updated.