Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Wrong Log severity in GKE & Google Cloud Logs #161

Open
socratesx-asimov opened this issue Jul 31, 2023 · 0 comments
Open

Wrong Log severity in GKE & Google Cloud Logs #161

socratesx-asimov opened this issue Jul 31, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@socratesx-asimov
Copy link

Your environment

Chart Version: 1.11.0

Helm Version: v3.12.2

Kubernetes Version: v1.26.4-gke.500

What happened?

The Logs in the Log Explorer are all listed as default severity, no matter if are info or error logs. Example:

image

What did you expect to happen?

It should list the logs of severity 1 as errors while the lower severity (3) it should be listed as info.

Steps to reproduce

  1. Deploy the Operator in GKE with default logLevel for sync & api.
  2. Check the connect-sync & connect-api logs in Logs Explorer.

Notes & Logs
@socratesx-asimov socratesx-asimov added the bug Something isn't working label Jul 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@socratesx-asimov