Metrics and Logs page navigation

Summary

When the troubleshooting panel navigates to a signal page (Metrics, Logs, Alerts) via a kebab menu query, the target page does not always display the expected content. Three variants of the same underlying problem have been identified.

Test executed for: alerts, metrics, logs, traces, several k8s objects. In general the issue is not present when we change a page, but when a query is executed, but if I discover new findings I will update the issue.

Environment

• OCP: 4.22.9
• COO: 1.5.1

Issues are most likely related to UI plugin shipped with COO (e.g. monitoring-plugin), but for sake of completeness I use:

• Troubleshooting panel: custom image from commit f31f5177e5e9d5e073857da453a971b3a9bedae7 (last one on main at moment of writing) .
• korrel8r: custom image from commit aa3536340fab027cd9e12f872dba0c355e217dd5.

Issue 1: Metrics page ignores second kebab click

Steps to reproduce:

1. Open the troubleshooting panel and run a neighborhood search (e.g. from a Deployment)
2. Click the kebab on the metric:metric node and select a query (e.g. {namespace="myreadings-dev", pod="catalog-service-..."})
3. The Metrics query browser opens and executes the PromQL query correctly
4. Go back to the troubleshooting panel and click a different metric query from the kebab (e.g. {k8s_namespace_name="myreadings-dev", k8s_pod_name="catalog-service-..."})

Expected: The Metrics page updates to show the new PromQL query and its results.

Actual: The URL updates with the new query0=... parameter, but the page immediately overwrites it back to the previous query. The user sees no change.

Issue 2: Logs page does not execute navigated query

Steps to reproduce:

1. Open the troubleshooting panel and run a neighborhood search
2. Click the kebab on the log:application node and select a LogQL query
3. The Logs page opens with the correct LogQL in the query input field

Expected: The query executes automatically and log results are displayed.

Actual: The URL changes, the query field shows the new LogQL, but the query is not executed. The user must manually click "Run Query" or press Enter to see results.

Reproduce the kebab-menu navigation from the troubleshooting panel for Metrics and Logs using the listed query examples. Trace how the target page reads URL query parameters and handles navigation, then verify that a second Metrics query replaces the first and that a navigated Logs query executes automatically. Confirm the behavior across the reported signal pages before considering it done.