1. Proposed title of this feature request

Request for improvements to be made to the Observe function of OpenShift
2. What is the nature and description of the request?

Customer recently upgraded to 4.10 and is unsatisfied with the features of Observe given that we removed the 3rd party ui's in 4.10 and 4.11 onward.

Here is a list I asked for. If you need me to split these up into separate RFE please ask.
So some of my issues with OCP Observe are:
Alerting:

• Always actually preferred this view over Alertmanager UI, BUT it doesn't show Alertmanager grouping so I still occasionally reference that versus Observer > Alerting. Without being able to see grouping it can be hard to see resulting Alertmanager grouping configs unless you just let them flood emails, webhooks or whatever and jump to those resulting places to see the grouping there.

Metrics:

• It lacks ability to select time ranges to search. Only allows my to look back up to 2w from 'Present'.
• While selecting a range from the graph the tooltip list of results relative to my mouse doesn't always show making it a guess of what second I'm looking to select.
• There's no information or setting for resolution.
• Ability to easily select specific series result from list below graph and reinvert that by selecting it again to have it show all on graph again. Instead have to keep jumping mouse from left to right side where you select 3-dot menu to Hide all series then back to far left to scroll back through a long list of metrics sometimes to select a small square.
• The series list has large wrapped text in table output which makes lists horrible on the eye vs list of key="value" which always helped me in Thanos/Prometheus to easily highlight/copy pieces of to add to my promQL query.

Dashboards:

• Grafana just looks and feels cleaner! Give Console a dark theme option. Else Observe's bright background isn't easy on the eyes!
• App teams are used to using Grafana and less likely to reference OCP's default dashboards because we had to deploy our own Grafana instance so we could load it with our own custom dashboards to incorporate custom metrics, app metrics, custom views of kube/ocp metrics, etc. since OCP doesn't allow us to load our own dashboards.

3. Why does the customer need this? (List the business requirements here)

Customer is unsatisfied with the current observe function in 4.10 and 4.11 especially considering that all 3rd party UI's were removed in these two versions and onward. They are aware of the UI improvement already made in.

https://issues.redhat.com/browse/MON-2196

4. List any affected packages or components.

Monitoring

Prometheus