this post was submitted on 19 May 2024
40 points (93.5% liked)

Programming

17133 readers
309 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
40
Logging Best Practices: The 13 You Should Know (2019) (www.dataset.com)
submitted 4 months ago by lysdexic@programming.dev to c/programming@programming.dev
7 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Aurenkin@sh.itjust.works 30 points 4 months ago

  1. Don’t Write Logs by Yourself (AKA Don’t Reinvent the Wheel)

  2. Log at the Proper Level

  3. Employ the Proper Log Category

  4. Write Meaningful Log Messages

  5. Write Log Messages in English

  6. Add Context to Your Log Messages

  7. Log in Machine Parseable Format

  8. But Make the Logs Human-Readable as Well

  9. Don’t Log Too Much or Too LittlE

  10. Think of Your Audience

  11. Don’t Log for Troubleshooting Purposes Only

  12. Avoid Vendor Lock-In

  13. Don’t Log Sensitive Information

The article goes into some nice detail on each of these but those are the 13 practices being advocated.