-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
Logging too verbose #9
Comments
hm basically moving these messages from Do you think we can output something else time-to-time just to know that the process isn't stuck when tailing servers? We can use |
Moving them to debug is the solution I would go with, but it sounds like you may want to keep these in your logs, so some sort of configuration option would accommodate both. As for outputting something just to know that it isn't dead – seems kind of hacky... not the right tool for the job. Perhaps we can output some statistics once in a while, but it still seems a bit forced. I definitely want to get rid of these from my logs though, because they drown out all the useful messages! |
is thinking on that ^^^ |
I'm tending to move these messages to the DEBUG level |
Good point. And it looks like Timing is included as part of default middleware, too. Well, I already have a branch where I moved these to debug for my own purposes, so let me just push that up and make a PR... |
What do you think of having the following messages show up only when the "verbose" option is specified:
Looking for new messages ...
No message found for ...
They are usually just noise, since they happen all the time, even when no jobs are being processed...
Or perhaps we can make it a config option, in the YML?
What do you think?
The text was updated successfully, but these errors were encountered: