Epic Goal

• Provide an easy access to the registry metrics and image streams metrics.

Why is this important?

• The registry is a core part of many workflows, and when its behavior suddenly changes, it's important to understand what else is changed: Did the number of incoming requests increase? Did storage become slower? Did the registry start reply with 500? How many requests are affected? The dashboard should help answer these questions and identify the cause of the problem.

Scenarios

1. A user reports the OpenShift administrator that an image couldn't be pushed because of a registry problem. The administrator wants to check how severe the problem is.
2. The administrator wants to check if the image pruner needs to be started.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

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>