At Fri, 31 Jan 2014 13:31:29 +0900, Matsuo Yoshinori wrote: > > Hitoshi & I discussed again. > > We have an another future idea that adds context id in the log message to > trace easily. > > i.e. > dog command logs: > Jan 31 13:19:34 sheep-01-00 sheepdog admin operation[1998]: dog cluster > format, context=c-aaaa > > sheep process logs: > Jan 31 13:19:34 INFO [main] rx_main(770) req=0x7f8c500008c0, fd=31, > client=127.0.0.1:46608, op=MAKE_FS, data=plain, context=c-aaaa > Jan 31 13:19:34 INFO [main] tx_main(770) req=0x7f8c500008c0, fd=31, > client=127.0.0.1:46608, op=MAKE_FS, result=00, context=c-aaaa > > where context=c-aaaa is some uniqe string or timestamp. > > It works like NDC(Nested Diagnostic Context. we are not focused on "nested" > though.) feature in log4j. > We can correct with tools such as syslogd and fluentd. > And then we can analyze the operation and troubles with grepped by context. > We are also trying to use tools like fluentd for helping our practical > operatin. Okay, it makes sense. I'm looking forward to the feature. Thanks, Kazutaka |