Fleet admins need a proper tool for analyzing their RHACM Hub (s) bottlenecks.

Why is this important?

A single hub may suffice in smaller environments, but as the scope of deployment grows to regional and global levels, real concrete numbers need to be analyzed quickly to check for performance bottlenecks

Scenarios
As a fleet admin, I want a quick but efficent way to analze overall performance
As a fleet admin, I want to understand in which areas of RHACM the bottleneck occurs

Acceptance Criteria
A public portal accessible across regions.
Do not retain customer specific data as part of the calculator tooling.
If there is an intersection of data that already exists within RH console/cloud redhat, please make it possible to read from that.

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.