-
Notifications
You must be signed in to change notification settings - Fork 36
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 logs #1012
improve logs #1012
Conversation
Signed-off-by: Danil Uzlov <DanilUzlov@yandex.ru>
Signed-off-by: Danil Uzlov <DanilUzlov@yandex.ru>
Signed-off-by: Danil Uzlov <DanilUzlov@yandex.ru>
Signed-off-by: Danil Uzlov <DanilUzlov@yandex.ru>
Signed-off-by: Danil Uzlov <DanilUzlov@yandex.ru>
Signed-off-by: Danil Uzlov <DanilUzlov@yandex.ru>
Signed-off-by: Danil Uzlov <DanilUzlov@yandex.ru>
Example of final version of logs:
|
Signed-off-by: Danil Uzlov <DanilUzlov@yandex.ru>
Signed-off-by: Danil Uzlov <DanilUzlov@yandex.ru>
Checked PR locally, I think we need additional discussion |
@glazychev-art Thanks for checking. Moving this PR to draft. @d-uzlov , @glazychev-art Let me know if you discuss it already. |
I have the following suggestions for further improvement:
We need to use the same logic as in |
Could we please break this up into smaller pieces. Shifting from INFO to DEBUG is a pretty small move Adding connection ids is a pretty small move It looks like they are getting conflated with much larger moves around changing the diff being used, moving to multi-line representations etc... which should be considered separately. |
@edwarnicke
As you mentioned, probably it would be better to split this PR in multiple ones. So we will probably do it in the following order:
|
What's the plan here for distinguishing between the call of 'request,close, register, unregister, find, etc' and the response? Knowing you, you've though this all the way through... curious the result :) |
It is actually very easy to change, because it is just a word printed in |
Description
Here is how nsmgr logs look after these changes: nsmgr-2021-07-08T210938+0700.log
Few examples:
grep <id>
, for examplegrep 017302e6-00bb-40e3-b60d-48c157d59e9f
, will give you full information about one of the connectionsHere is how nsmgr logs with log level set to
info
look like: nsmgr-2021-07-08T212330+0700.logThese logs are actually not as useful as I had hoped.
We have few issues with them:
info
level.We can probably add log level as an argument for this method.
I'm really not sure if we need to do anything with these issues in context of this task, though. Probably not.
Issue link
Closes #1008
How Has This Been Tested?
Types of changes