Epic Goal

As an operator of ACM/MCE, I should be able to export ACM metrics to promoetheus and see import times over time, associated to the cluster name.

Why is this important?

When ACM is used to provide hypershift service as a SAAS offering, the import times for hosted clusters to come under management can be useful to track over time as the SAAS offering grows.

A hostedcluster under management will have policies and configurations applied. If the import time is degraded due to a subcomponent, either from ACM/MCE itself or external dependencies like certificate provided to ingress, then the SAAS should have a way to track this metric.

Initially, the import time can be the duration between the creationTimestamp of the managedcluster CR and the lastUpdateTime of the Availiable condition of the managedcluster CR (in adhoc testing, this seems to be a good measure of this duration).

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. ...

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.