Skip to content
This repository has been archived by the owner on Nov 27, 2024. It is now read-only.

Flags for logging levels and logging to console #151

Closed
wants to merge 9 commits into from

Conversation

andrew-nowak
Copy link
Contributor

@andrew-nowak andrew-nowak commented Dec 13, 2016

-L=<level> sets logging level
-d sets logging level to 'debug' (highest level), overwriting -L
--logconsole also logs to console (default is not to log)

Resolves #120

@mgcam
Copy link
Member

mgcam commented Dec 15, 2016

We might want to be even more flexible and to give an option to have either console logger or file logger or both. It would also be good to have a custom log file location/name.

Andrew Nowak added 2 commits December 16, 2016 17:03
There is a long-standing (multiple years) bug with winston that logging
to file may not necessarily finish before a process.exit(). Avoid this
by allowing logging to stderr, and expect users to redirect as necessary.
@andrew-nowak
Copy link
Contributor Author

As in commit message in 7d61fa2 - the File transport in Winston will not always flush all the logs to the file before process.exit is called. Instead, we won't log to file (so no logs are lost), bu this means that we need to update deployment processes to redirect stderr to a logfile.

@andrew-nowak andrew-nowak mentioned this pull request Dec 20, 2016
@andrew-nowak
Copy link
Contributor Author

Replaced by #153

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants