News for hackers. Stuff that matters.

A comment on Discussion: structured, leveled logging. Parent comment

Re:Discussion: structured, leveled logging by rcarmo on Sunday September 11, 2022 @02:40PM (#32802131)
Many tracing libraries get their data off logging libraries. Logging doesn't always mean "whoa, let's stop everything and write to a file", it is often a matter of buffering data or increasing counters until data can be sent out in various fashions.

Log files are just one of those.

[ Parent | on HN ]
Re:Discussion: structured, leveled logging by glenjamin on Sunday September 11, 2022 @03:16PM (#32802415)
The key difference is my experience is not about destination - backends are as flexible as you say

One key difference is having an event name + properties, rather than a human-readable description and maybe some fields if you’re lucky

Another key difference is wrapping units of work rather than just scattering log lines in places you think need them somewhat arbitrarily

[ Parent | on HN ]
Re:Discussion: structured, leveled logging by jayd16 on Sunday September 11, 2022 @04:05PM (#32802801)
>One key difference is having an event name + properties [...] Another key difference is wrapping units of work [...]

Modern "enterprise" logging libraries already work this way, don't they?

[ Parent | on HN ]
Re:Discussion: structured, leveled logging by rcarmo on Sunday September 11, 2022 @03:27PM (#32802490)
Most decent logging frameworks allow for structured output. That change came about roughly when NewRelic became "the thing" to use.
[ Parent | on HN ]
Re:Discussion: structured, leveled logging by markmark on Sunday September 11, 2022 @07:29PM (#32804245)
You probably need to look into modern logging if you think that's how logging still works.
[ Parent | on HN ]