Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Could not find SLF4J logs in Log Explorer for any cloud run application

Hi,
We have deployed our Spring Boot application which has SLF4J logging in Google Cloud Run, till 18th of November we were able to see the logs (log.info, log.warn, log.error and sysout) but when we did one change in 
Log Router -> Choose logs to include in sink
we updated query to exclude some logs after this change we were not getting the logs in our log explorer, so we reverted the change back to the same. Now still after reverting the change we are not getting the logs in our log explorer.
Can anyone help us in sorting this out. We want that all logs should be displayed in our log explorer

sahushubham768_0-1732092888426.png

 

Solved Solved
0 1 198
1 ACCEPTED SOLUTION

Hi @sahushubham768 ,

We’re currently aware of an issue with Cloud Logging queries failing when using filters, and we’re working to address this. In the meantime, I recommend performing the following troubleshooting actions:

If none of these resolve the issue, you can file a detailed bug report through the Issue Tracker. Include steps to replicate, configuration settings, screenshots, and other details of the issue to help us investigate.

While there isn’t a specific timeframe for resolution, once we've fixed an issue in production we'll indicate this and then update and close the bug. You may also follow our Google Group or Slack Community for more updates.

I hope this helps!

View solution in original post

1 REPLY 1

Hi @sahushubham768 ,

We’re currently aware of an issue with Cloud Logging queries failing when using filters, and we’re working to address this. In the meantime, I recommend performing the following troubleshooting actions:

If none of these resolve the issue, you can file a detailed bug report through the Issue Tracker. Include steps to replicate, configuration settings, screenshots, and other details of the issue to help us investigate.

While there isn’t a specific timeframe for resolution, once we've fixed an issue in production we'll indicate this and then update and close the bug. You may also follow our Google Group or Slack Community for more updates.

I hope this helps!

Top Solution Authors