-
Bug
-
Resolution: Done
-
Blocker
-
Logging 5.6.0, Logging 5.5.z
-
False
-
None
-
False
-
NEW
-
VERIFIED
-
-
Description of problem:
Deploy logging and use loki as the log store, then enable console plugin. When checking infra logs in Developer Console, always get `No datapoints found`:
From the logs in querier and query-frontend pod, it sets `org_id=application` when checking infrastructure logs:
level=info ts=2023-01-03T08:47:35.994450326Z caller=metrics.go:143 component=querier org_id=application latency=fast query="{log_type=~\".+\", kubernetes_namespace_name=\"openshift-cluster-version\", kubernetes_namespace_name=~\"default|kube-node-lease|kube-public|kube-system|logging-loki|openshift|openshift-apiserver|openshift-apiserver-operator|openshift-authentication|openshift-authentication-operator|openshift-cloud-controller-manager|openshift-cloud-controller-manager-operator|openshift-cloud-credential-operator|openshift-cloud-network-config-controller|openshift-cluster-csi-drivers|openshift-cluster-machine-approver|openshift-cluster-node-tuning-operator|openshift-cluster-samples-operator|openshift-cluster-storage-operator|openshift-cluster-version|openshift-config|openshift-config-managed|openshift-config-operator|openshift-console|openshift-console-operator|openshift-console-user-settings|openshift-controller-manager|openshift-controller-manager-operator|openshift-dns|openshift-dns-operator|openshift-etcd|openshift-etcd-operator|openshift-host-network|openshift-image-registry|openshift-infra|openshift-ingress|openshift-ingress-canary|openshift-ingress-operator|openshift-insights|openshift-kni-infra|openshift-kube-apiserver|openshift-kube-apiserver-operator|openshift-kube-controller-manager|openshift-kube-controller-manager-operator|openshift-kube-scheduler|openshift-kube-scheduler-operator|openshift-kube-storage-version-migrator|openshift-kube-storage-version-migrator-operator|openshift-logging|openshift-machine-api|openshift-machine-config-operator|openshift-marketplace|openshift-monitoring|openshift-multus|openshift-network-diagnostics|openshift-network-operator|openshift-node|openshift-nutanix-infra|openshift-oauth-apiserver|openshift-openstack-infra|openshift-operator-lifecycle-manager|openshift-operators|openshift-operators-redhat|openshift-ovirt-infra|openshift-ovn-kubernetes|openshift-route-controller-manager|openshift-service-ca|openshift-service-ca-operator|openshift-user-workload-monitoring|openshift-vsphere-infra|test\"} | json" query_type=limited range_type=range length=30m0s start_delta=47m35.994445633s end_delta=17m35.994445797s step=14s duration=3.043072ms status=200 limit=100 returned_lines=0 throughput=0B total_bytes=0B total_entries=0 queue_time=0s subqueries=1 cache_chunk_req=0 cache_chunk_hit=0 cache_chunk_bytes_stored=0 cache_chunk_bytes_fetched=0 cache_index_req=0 cache_index_hit=0 cache_result_req=0 cache_result_hit=0 level=info ts=2023-01-03T08:47:35.88744008Z caller=engine.go:199 org_id=application msg="executing query" type=range query="{log_type=~\".+\", kubernetes_namespace_name=\"openshift-cluster-version\", kubernetes_namespace_name=~\"default|kube-node-lease|kube-public|kube-system|logging-loki|openshift|openshift-apiserver|openshift-apiserver-operator|openshift-authentication|openshift-authentication-operator|openshift-cloud-controller-manager|openshift-cloud-controller-manager-operator|openshift-cloud-credential-operator|openshift-cloud-network-config-controller|openshift-cluster-csi-drivers|openshift-cluster-machine-approver|openshift-cluster-node-tuning-operator|openshift-cluster-samples-operator|openshift-cluster-storage-operator|openshift-cluster-version|openshift-config|openshift-config-managed|openshift-config-operator|openshift-console|openshift-console-operator|openshift-console-user-settings|openshift-controller-manager|openshift-controller-manager-operator|openshift-dns|openshift-dns-operator|openshift-etcd|openshift-etcd-operator|openshift-host-network|openshift-image-registry|openshift-infra|openshift-ingress|openshift-ingress-canary|openshift-ingress-operator|openshift-insights|openshift-kni-infra|openshift-kube-apiserver|openshift-kube-apiserver-operator|openshift-kube-controller-manager|openshift-kube-controller-manager-operator|openshift-kube-scheduler|openshift-kube-scheduler-operator|openshift-kube-storage-version-migrator|openshift-kube-storage-version-migrator-operator|openshift-logging|openshift-machine-api|openshift-machine-config-operator|openshift-marketplace|openshift-monitoring|openshift-multus|openshift-network-diagnostics|openshift-network-operator|openshift-node|openshift-nutanix-infra|openshift-oauth-apiserver|openshift-openstack-infra|openshift-operator-lifecycle-manager|openshift-operators|openshift-operators-redhat|openshift-ovirt-infra|openshift-ovn-kubernetes|openshift-route-controller-manager|openshift-service-ca|openshift-service-ca-operator|openshift-user-workload-monitoring|openshift-vsphere-infra|test\"} | json" length=17m35.706s step=14s
Version-Release number of selected component (if applicable):
loki-operator.v5.6.0
loki-operator.5.5.6
How reproducible:
Always
Steps to Reproduce:
- deploy logging, use lokistack as the log store
- log in to Administrator console with cluster-admin, and enable console plugin
- switch to Developer console, then set project `openshift-cluster-version` and go to Observe --> Aggregated Logs
Actual results:
Get `No datapoints found` when checking infra logs in Developer Console.
Expected results:
Should show logs in the project.
Additional info:
- links to
- mentioned on
