Value Statement

We should ensure that we can alert on the client (spoke) for ACM metrics collector metrics push issues.

We should ensure that we can log and/or alert with enough context on the Hub to identify managed clusters that are having problems sending metrics.

It is useful to identify easily problematic spoke clusters.

Definition of Done for Engineering Story Owner (Checklist)

• Spokes which cannot push metrics fire an alert
• When I view error logs of observatorium-api I am able to someway identify the managed cluster that is triggering these errors!

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.