-
Notifications
You must be signed in to change notification settings - Fork 117
[bugfix] Fix logging crash when increasing verbosity level #1275
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
Conversation
ekouts
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
vkarak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix is working however there are two things missing or need more thinking:
- We will need a unit test to reproduce the bug.
- The
check_job_completion_timeis not sent over to Graylog. Only the raw time is sent. I don't know if we can do something for that, because what is sent to Graylog are theextrasand not the formatted text. I don't know if formatting the message and sending it is the correct way to deal with that or formatting at the Graylog site is the best solution, but I kind of think the second one is at least more correct.
…/RFC3339Formatter
…/RFC3339Formatter
vkarak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also add an entry in the documentation explaining the new field?
|
@victorusu I've updated the documentation. |
This PR adds an additional field to the
LoggerAdapterclass as suggested by @vkarak. This new field holds the original UNIX time and it is used to format thecheck_job_completion_timefield.Fixes #1261
Fixes #1265