|
|
|
|
|
by packetlost
565 days ago
|
|
I started developing a tracing/span library that does just this: log messages are "global" (to a system/org) hierarchical "paths" + timestamp + a tagged union. The tagged union method allows you to have zero or more internal parameters that can be injected into a printf (or similar style) format string when printing, but the message itself is only a few bytes. The benefits to this approach is it's dramatically easier to index and cheaper to store at any scale. One thing I think people don't appreciate about logging efficiency is it enables you to log and store more and I think many don't appreciate how much even modest amounts of text logs can bog down systems. You can't read anything, but you filters easy and powerful and you can't filter something that doesn't exist. |
|
How did your solution work out in terms of adoption by others? Was it a large team using it? What did those people say? Really curious!