-
Notifications
You must be signed in to change notification settings - Fork 24
Added a debugging log stream for pretty console logging #49
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
|
Hm. Not sure we should use node-bunyan-prettystream, as it looks like it's not maintained any more - last commit was 2 years ago and there are 4 open issues and 11 PRs opened against it. Other forks, like hadfieldn's include some of the PRs and some other improvements. The main drawback I see in the original module is the lack of support for circular references. |
|
I'm also not in favour of this being a dependency for |
|
Also, note that |
|
@d00rman hm, the If yurik would agree on the ticket, I'll close this PR. |
|
@d00rman Actually, I've found a use-case for this. When running tests, |
|
@Pchelolo I think that's a minor corner case and that in that context we'd be just adding bloat to the package. @wikimedia/services thoughts? |
|
I'm also leaning towards keeping things simple. The mocha use case seems to be pretty borderline. |
|
I've reopened this pull request as @nyurik found one more good use-case for this capability: https://phabricator.wikimedia.org/T133611 Also updated the patch according to all the comments. |
|
Published as v1.2.2 |
In this ticket an option for pretty human-readable console logs for service-runner is requested. I find reading JSON logs painful too, so here's a
debugstream that outputs nice color-coded logs with nice expanded stack-traces etc.Usage: simply add a
type: debugstream to logger config.