| |||||||||||||
They should be paying attention to the lumberjack projectThey should be paying attention to the lumberjack projectPosted Apr 17, 2012 16:38 UTC (Tue) by k8to (subscriber, #15413)In reply to: They should be paying attention to the lumberjack project by dlang Parent article: Toward more reliable logging
To be fair, a list of say filenames isn't hard to do in kv pairs.
filename:foo filename:bar filename:baz
Sure, that's more trouble to parse than assuming you can't have repeats, but it's not much work.
However, it starts getting tedious if you need to say something like:
severity:fatal message="corruption in filesystem regarding following items" filename:foo inode:3 filename:bar inode:6 filename:baz inode:8
At this point you really want more structure, or else the consuming end has to intuit to group things.
(Log in to post comments)
They should be paying attention to the lumberjack project Posted Apr 21, 2012 8:19 UTC (Sat) by neilbrown (subscriber, #359) [Link]
.... filename-1:foo inode-1:3 filename-2:bar inode-2:6 filename-3:bar inode-3:8
Explicit structure embedded in the names of name:value pairs.
Yes, it's ugly. But it's simple and if most cases don't need any real structure, then the ugliness will hardly be noticed.
|
|||||||||||||