-
Notifications
You must be signed in to change notification settings - Fork 17
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
Info level is too chatty for this sleep message, debug is good #41
Info level is too chatty for this sleep message, debug is good #41
Conversation
@komealy, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
134ca8d
to
9bbe0b8
Compare
@komealy, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
9bbe0b8
to
b19946e
Compare
@komealy, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
b19946e
to
bf3acf9
Compare
@komealy, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
bf3acf9
to
72c5b4f
Compare
@komealy, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
Signed-off-by: Kris O'Mealy <komealy@hotmail.com> Info level is too chatty for this sleep message, debug is good. Signed-off-by: Kris O'Mealy <komealy@hotmail.com>
72c5b4f
to
9553ec4
Compare
@komealy, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
I tried all the things suggested by Github to allow my real email to be the author of this git commit, but it still only ended up as the noreply email... |
Looks like the original commit was the issue, I had to start fresh after setting all my github email settings. Then my email is now the author in the new PR #42 |
Having this in Info level produces thousands of messages per minute in a production level stream that is operating appropriately. Knowing this for debug purposes is good enough. We shouldn't be overloading log processing pipelines with this much repetitive spam in info level.
Resolves #40