-
Notifications
You must be signed in to change notification settings - Fork 699
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
Improve meta information in log messages to make it easier to debug jobs #765
Conversation
…obs. * Use <namespace>.<name> as opposed to <namespace>/<name>; the former is more consistent with K8s style. * Add functions for constructing loggers for the pod and unstructured meta information. This will allow us to appropriately tag a number of log messages with meta information. * Update a bunch of log messages which weren't logging info with appropriate meta information. * Make json log formatting the default; this was the case for v1. json logging should be the default because otherwise we lose the meta information in the logs. With json logs its always possible to filter/reformat the log entries if you don't care about the metainformation. Related to: kubeflow#24 Use logrus kubeflow#635
/assign @gaocegege |
Travis tests have failedHey @jlewi, 2nd Buildgometalinter --config=linter_config.json --vendor ./...
3rd Buildgometalinter --config=linter_config.json --vendor ./...
|
/lgtm |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jlewi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Use . as opposed to /; the former
is more consistent with K8s style.
Add functions for constructing loggers for the pod and unstructured meta
information. This will allow us to appropriately tag a number of log
messages with meta information.
Update a bunch of log messages which weren't logging info with
appropriate meta information.
Make json log formatting the default; this was the case for v1.
json logging should be the default because otherwise we lose the meta
information in the logs. With json logs its always possible to filter/reformat
the log entries if you don't care about the metainformation.
Related to:
#24 Use logrus
#635
This change is