Status Update
Comments
ka...@google.com <ka...@google.com>
ab...@likemagic.tech <ab...@likemagic.tech> #2
Looks like an integration issue.
For some reason the filters send to Logs Explorer
have changed
labels.k8s-pod/app.kubernetes.io/component="backend"
vs
labels."k8s-pod/app_kubernetes_io/component"="backend"
ma...@google.com <ma...@google.com> #3
Hello,
Thanks for reaching out to us!
The Issue request has been created and the Product Engineering Team is working on this issue. Right now, there is no ETA to this request. Thank you for your trust and continued support to improve Google Cloud Platform products.
In case you want to report a new issue, please do not hesitate to create a new
Thanks and Regards,
Mahaboob Subhani
Google Cloud Support
ar...@podimo.com <ar...@podimo.com> #4
We are experiencing the same issue, it's a pretty big issue since now you have more manual work to do in order to retrieve logs for each affected service. When there will be any ETA?
al...@google.com <al...@google.com> #5
jo...@dakota.xyz <jo...@dakota.xyz> #6
vi...@google.com <vi...@google.com> #7
At the moment the automatically generated query for viewing GKE workload logs in Cloud Logging uses periods (".") instead of underscore ("_") in Kubernetes labels.
While the fix is rolled out users can perform one of the following:
-
Manually editing the query to use underscores ("_") instead of periods (".")
For example if the auto generated query has labels like
labels.k8s-pod/app.kubernetes.io/env="test"
Replace periods (".") with underscores ("_") while using quotes for the label
labels."k8s-pod/app_kubernetes_io/env"="test"
-
Remove the generated filters for workload labels and add a filter for pod name:
For example if the auto pod name is
test-pod-787784f987-ww2fj
, then use a filter like below:resource.labels.pod_name:"test-pod-787784f987-"
Note: to make sure all pods of a deployment replica-set is selected it is important to keep the replica-set number as well, in the above example it is
787784f987
ol...@adorama.com <ol...@adorama.com> #8
containers:
- command:
- /fluent-bit-gke-exporter
- --pod-label-dot-replacement=_
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
When I jump on GKE into a Workload I can't see logs in tab log. Also when I click on "View in Log Explorer" I can't see the logs. But if I switch to a specific replicaset or a Pod, I can see all logs belongs to this kind.
In our Application we set following labels:
But a log contains following labels:
labels.k8s-pod/app_kubernetes_io/instance
labels.k8s-pod/app_kubernetes_io/name
The issue here is that on workload tab logs and also by jumping to "View in Log Explorer" this is set:
labels.k8s-pod/
labels.k8s-pod/
So the dots aren't replaced by underscore
What you expected to happen:
Under this tab and by jumping to "View in Log Explorer" you should normally see all logs that belongs to this deployment.
Steps to reproduce:
Set these labels in the deployment manifest:
Set these selectorLabels in the deployment manifest:
Other information (workarounds you have tried, documentation consulted, etc):