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
Production logs include timestamps (Switch to Winston) #209
Comments
@skddc I had a look at this today, and sockethub isn't actually logging any timestamps that I can see. Is it coming from somewhere else? |
Maybe some node.js default? |
@skddc note node.js itself, but is it set up on the server to use some kind of service which keeps the process running? ( always, etc.) |
systemd is adding the first timestamp in its journal. This issue is about the extra timestamp added by Sockethub. |
@skddc it seems to be the There doesn't seem to be any way to turn this off at the moment, though there does seem to be some discussion about it in this issue: debug-js/debug#370 Opened this issue: debug-js/debug#453 |
Cool. |
Or possibly switch to Winston as part of the effort to implement log levels #225 |
That one is also being added to armadietto atm: remotestorage/armadietto#49 |
When using systemd, logs from journalctl contain duplicate timestamp data, because systemd adds those by itself already:
Would probably make sense to use
NODE_ENV
for some of these presets, and only show timestamps indevelopment
for example.The text was updated successfully, but these errors were encountered: