Log format
See original GitHub issueIs your feature request related to a problem? Please describe. What’s the point of this line: https://github.com/ArkEcosystem/core/blob/9b1333487ea1556280f25d39254874db874a91e0/packages/core-logger-winston/lib/formatter.js#L36
Why don’t you just remove it, the log looks strange?
Describe the solution you’d like
return [${timestamp}][${level}]: ${message}
Describe alternatives you’ve considered
Additional context
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
6 Common Log File Formats - CrowdStrike
Commonly Used Log Formats · JSON · Windows Event logs · CEF · CLF · ELF · W3C.
Read more >Common Log Format - Wikipedia
For computer log management, the Common Log Format, also known as the NCSA Common log format, (after NCSA HTTPd) is a standardized text...
Read more >LOG - File Format Docs
The LOG file format records the typical events that occur either in an operating system, messages between different users of a communication software...
Read more >mod_log_config - Apache HTTP Server Version 2.4
The format argument to the LogFormat and CustomLog directives is a string. This string is used to log each request to the log...
Read more >Log Formatting: 7 Best Practices for Readable Log Files | Scalyr
1. Make Your Log Entries Meaningful With Context · 2. Use a Standard Date and Time Format · 3. Use Local Time +...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Log output mustn’t be unnecessary hard to read. It’s easier to parse visually with the whitespace. Especially if you spent a lot of time looking at walls of text.
I’m not saying the current format can’t be improved, but let’s not make it worse.
Also your proposal is not even aligned properly. 👎
Well,
sounded offensive. OK maybe I overreacted, I apologize.
How about: const lineSpacer = ‘\t’