Description of problem:

Clicking `See related logs` in console always get irrelevant logs, for example:

Alert details:

After clicking `See related logs`, the query string is:

{ kubernetes_namespace_name="default", kubernetes_pod_name="bad-config-deployment-56b4997dd9-w42rf", log_type="infrastructure" } | json 

The pod name in query string is not the name of the pod which makes the alert firing. 

Another example:

The query string is:

{ kubernetes_namespace_name="openshift-logging", kubernetes_pod_name="cluster-logging-operator-6d7bdcbbd7-gfmjt", log_type="infrastructure" } | json 

Version-Release number of selected component (if applicable):

openshift-logging/logging-view-plugin-rhel9/images/v5.8.1-6

openshift-logging/cluster-logging-rhel9-operator/images/v5.8.1-18

quay.io/korrel8r/operator-bundle:v0.0.7

4.15.0-0.nightly-2023-12-04-162702

How reproducible:

Always

Steps to Reproduce:

1. deploy lokistack
2. deploy korrel8r via operator
3. make some alerts firing

Actual results:

Clicking `See related logs` in console always get irrelevant logs.

Expected results:

Clicking `See related logs` in console should get logs correctly.

Additional info: