4 ms·
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
by rcarmo 4y ago
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.
- glenjamin 4y agoThe 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
- rcarmo 4y agoMost decent logging frameworks allow for structured output. That change came about roughly when NewRelic became "the thing" to use.
- jayd16 4y ago>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?
- markmark 4y agoYou probably need to look into modern logging if you think that's how logging still works.