Epic Goal

Override cluster label for ACM hub for metrics sent to a remote endpoint.

Why is this important?

Users have monitoring platforms which are fed metrics from potentially many Kubernetes clusters, some OCP and some not. Consequently, it is necessary to group metrics by a specific cluster name. Currently, metrics from an ACM hub have the cluster label hard-coded to "local-cluster", resulting in the user having to implement workarounds such as additional labels to avoid incorrect groupings on their remote dashboards. 

Scenarios

1. This is about user over-ride on the hub cluster metrics label, but not actually change the local-cluster hub name itself.

>> maybe there's a way to change the value of the "cluster" label on a metric before it's sent out to some remote endpoint, but otherwise leave the "cluster" label intact on the hub itself.

Acceptance Criteria

• The user is able to override the cluster label for metrics being written to a remote endpoint.
• The value of the cluster label in the remote endpoint matches the overridden value for all metrics from the ACM hub.

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 - Downstream documentation merged: <link to meaningful PR>