Slack thread: https://redhat-internal.slack.com/archives/C07RV4GPQSV/p1745537301185819

Preparation:

• OCP4.18
• Install ACM

1. Go To Operators > OperatorHub
2. Search for Advanced Advanced Cluster Management for Kubernetes
3. Install with all default values
4. Install finished with a request to create a Multicluster engine for Kubernetes

1. Create Multicluster
2. Wait for some seconds / minute and verify a warning message on the right top corner
3. Web console update is available. There has been an update to the web console. Ensure any changes have been saved and refresh your browser to access the latest version. Refresh web console link
4. Click on Refresh web console

1. Run acm.txt and acm1.txt (rename to .sh to configure and create some fake alerts)

• Install Virtualization

1. Go To Operators > OperatorHub
2. Search for Openshift Virtualization
3. Install with all default values
4. Install finished with a request to create a HyperConverged

1. Create it with default values
2. Wait for some seconds / minute and verify a warning message on the right top corner

1. Web console update is available. There has been an update to the web console. Ensure any changes have been saved and refresh your browser to access the latest version. Refresh web console link
2. Click on Refresh web console

1. Verify Administrator / Developer perspective

• • Virtualization option available

• Install COO
  • Enable Troubleshooting Panel UIPlugin on COO
    • https://github.com/rhobs/observability-operator/blob/main/docs/user-guides/observability-ui-plugins.md#troubleshooting-panel
  • Enable Monitoring UIPlugin on COO
    • https://github.com/rhobs/observability-operator/blob/main/docs/user-guides/observability-ui-plugins.md#monitoring

1. On ACM
   1. Click on All Clusters > Observe > Alerting
   2. Click on 9dots Icon > Signal Correlation to open Troubleshooting panel
   3. On Troubleshooting panel, notice that Focus button is enabled
   4. Click on Show query to check details
   5. Click on Focus button, notice that query field changes
      1. However, no correlation signal is rendered
      2. 
2. On Virtualization
   1. Change perspective to Virtualization
   2. Click on Observe > Alerting
   3. Click on 9dots > Signal Correlation
   4. On Troubleshooting panel, notice that Focus button is enabled
   5. Click on Show query to check details
   6. Click on Focus button, notice that query field changes
      1. However, no correlation signal is rendered
      2. 

Actual Result: Per gbernal@redhat.com, In principle the troubleshooting panel is not supported in ACM or virtualization perspectives. We probably need to make adjustments on the UI and the korrel8r backend so it works correctly. But it "should" work for a single spoke cluster.

Per rh-ee-pyurkovi: I would say make the entire troubleshooting UI disappear within the side panel and maybe show an empty state in the side panel. @Foday may be the person to decide on that 

Technical solution suggestion by Gabriel:

• hide the Signal Correlator from masthead when  we are in Virt and ACM perspectives - but it involved Console team

• We will need to work anyway in the empty state bc user can have be in Admin perspective, have Troubleshooting panel opened and switch to Virt or ACM perspective and it will be there anyway, even without the link. So, if the user click on Focus button, we should have anything to mention to user.