Skip to content

Optionally disable timestamps #453

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
silverbucket opened this issue May 10, 2017 · 4 comments
Closed

Optionally disable timestamps #453

silverbucket opened this issue May 10, 2017 · 4 comments

Comments

@silverbucket
Copy link

silverbucket commented May 10, 2017

When a node process is managed by systemd, systemd already provides timestamps in addition to the automatic prepending of timestamps by debug when not in a TTY. Therefore each line has double-timestamps.

Mar 19 16:29:19 dev sockethub[8187]: Sun, 19 Mar 2017 16:29:19 GMT express:router:layer new '/complete'
Mar 19 16:29:19 dev sockethub[8187]: Sun, 19 Mar 2017 16:29:19 GMT express:router:route get '/complete'
Mar 19 16:29:19 dev sockethub[8187]: Sun, 19 Mar 2017 16:29:19 GMT express:router:layer new '/'
Mar 19 16:29:19 dev sockethub[8187]: Sun, 19 Mar 2017 16:29:19 GMT express:router:route new '/delayed'
Mar 19 16:29:19 dev sockethub[8187]: Sun, 19 Mar 2017 16:29:19 GMT express:router:layer new '/delayed'
Mar 19 16:29:19 dev sockethub[8187]: Sun, 19 Mar 2017 16:29:19 GMT express:router:route get '/delayed'
Mar 19 16:29:19 dev sockethub[8187]: Sun, 19 Mar 2017 16:29:19 GMT express:router:layer new '/'

DEBUG_NOTIMESTAMPS=1 or something similar would be a great feature to have.

@EirikBirkeland
Copy link
Contributor

Timestamps show up in PM2 also. I am interested in toggleable, namespaced logging, not timestamps.

@amejiarosario
Copy link

amejiarosario commented Aug 12, 2017

This is an issue in Heroku as well. Please check out the PR to solve this
cc: @TooTallNate @EirikBirkeland

@EirikBirkeland
Copy link
Contributor

I forked and changed the code, works for me :) Thanks though.

@Qix-
Copy link
Member

Qix- commented Jun 20, 2018

Closing in favor of #582. Please move discussion there.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

No branches or pull requests

4 participants