WHY
We need to ensure that any monitoring functionality that RHOAM is currently getting from OO is also supported through OBO. We need to identify any potential gaps early in the migration process so we can request that the missing features be supported by OBO.

WHAT
Determine what features are supported in OO but are not supported in OBO. Once the gaps have been identified, determine which features we will need to request OBO to support.

HOW
First install an instance of RHOAM and wait for the OO monitoring stack to provision. Then create a MonitoringStack CR in the openshift-observability-operator Namespace and wait for the OBO monitoring stack to provision. Compare the .spec's of the OO and OBO Prometheus and Alertmanager CRs and document any components that are present in OO but not in OBO.

Determine how to reconcile the differences and highlight any features that are currently not supported by OBO that RHOAM will need to preserve its existing monitoring functionality.

DONE

• Identified gaps between OO and OBO monitoring stack capabilities
• Determined how to mitigate gaps and/or requested the missing features be supported by OBO