Closed bion closed 9 years ago
Word.
Fantastic picture!
Be sure to include an easily searchable keyword for each type of log, as well as a timestamp. This will make it easy to answer questions like "how many requests were made in the last week?" by using simple command line tools like grep.
also, make the timestamp easy to parse, as oppose to human readable.
cool. know of any examples that show good logging practices?
uhhh not off the top of my head, you can try googling.
for now i don't think you need to bother with any of the really heavy-weight tools out there like winston or bunyan. but they're good to know about.
okay cool. yeah, i'm googling stuff now.
On Tue, Nov 18, 2014 at 2:47 PM, Bion Johnson notifications@github.com wrote:
for now i don't think you need to bother with any of the really heavy-weight tools out there like winston or bunyan. but they're good to know about.
— Reply to this email directly or view it on GitHub https://github.com/andyjac/lastfm_top_albums/issues/14#issuecomment-63560371 .
Done.
Log everything, always. Log every request you get from the client and every response you get from lastfm. Start logging less only when it becomes a performance issue.