Alert navigation

Console has two alert pages:

• Rule (/monitoring/alertrules/{id}) — the alerting rule and all of its current firings. This is where Observe → Alerting → Alerts takes you when you click a row in the list.
• Instance (/monitoring/alerts/{id}?labels…) — one firing. Console only goes here after you pick a specific firing, passing that firing’s full label set. The page shows content only if exactly one firing matches the query parameters; otherwise it is blank.

The panel always builds the instance URL, using the korrel8r query as the query parameters.So:

• Start from (or navigate to) a query that matches one firing → the instance page works.
• Query matches several firings, or only has alertname (aggregated node, rule with multiple instances) → empty page.

This could be improved returning instance URL when the query uniquely identifies a firing; rule URL when it does not. The panel already understands both paths when reading the current page.

Start at the troubleshooting panel's navigation logic that builds the monitoring alert URL, and review how it handles the korrel8r query and the two alert paths. Verify behavior with a query matching one firing, then with multiple firings or only alertname. Done means unique firings use the instance URL, while non-unique queries use the rule URL.