-
Notifications
You must be signed in to change notification settings - Fork 2k
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.
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
[Bug]: logFormat=json creates events without contextual information #7574
Comments
Hi @hafe thanks for reporting! Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂 Cheers! |
@hafe Can you please provide exact repro steps for this please with the event you're observing in logs? |
just switched logFormat from glog to json and file/line is no longer present in log messages |
Example with glog: I0330 07:06:24.132037 1 leaderelection.go:257] attempting to acquire leader lease default/nic-nginx-ingress-leader-election... Example with json: I0330 07:03:07.868148 1 leaderelection.go:257] attempting to acquire leader lease default/nic-nginx-ingress-leader-election... No file and line and leader election still uses glog it seems |
Hi @hafe , Thank you for the update on this, we will investigate this soon. |
Version
edge
What Kubernetes platforms are you running on?
Kind
Steps to reproduce
No file and line present in NIC logs when logFormat is "json". File and line are present when "glog" is configured.
Structured logging in JSON is nice but without file and line it is not very practial to use.
The text was updated successfully, but these errors were encountered: