-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Add trace level log support in containerd. #2028
Comments
Why not just use debug level instead of adding more levels. we already have fatal, error, warn, info, and debug. I think we can find an existing one |
Here is our use case:
Is there any other way to solve this? Or shouldn't we add "trace level" logs? |
So trace is a level below debug? |
@crosbymichael that's how it is treated in other logging library. Usually the expectation is that that level will log every entry and exit within a function. |
ok, sounds good to me. @stevvooe any thoughts ? |
@crosbymichael Do we want to upstream the |
That would be ideal |
@stevvooe This was proposed several times in logrus:
Even several PRs:
I just don't understand why they don't want it... |
@Random-Liu I am a maintainer there... I think the problem with sirupsen/logrus#652 is that it is not backwards compatible for those using the interface to define a logger type. I'll LGTM it and see if that is a concern. |
Description
logrus doesn't support trace. But it is useful in general containerd/cri#548.
In https://github.com/containerd/cri-containerd/pull/547/files#diff-1135f265d25e96e557b8114567653176 we added the library to support
Trace
in cri-containerd.Can we have this library in containerd? Or can we at least accept
trace
inlog-level
flag?Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Output of
containerd --version
:The text was updated successfully, but these errors were encountered: