Why is this enhancement useful?
Currently ShiViz can only parse logs strictly in the format generated by
ShiVector, in which each log event is a single log line followed by a timestamp
line structured as follows:
_localHostId_ { "_host1_" : _time1_, "_host2_" : _time2_, ..., "_hostN_" :
_timeN_ }
An example of this format is:
{{{
24.22.130.14 5/27/2013 10:56:22 AM GET /timeline uid=alice location=kansas
alice {"alice":5, "loadBalancer": 4, "eastDC":8, "westDC": 3}
}}}
However, ShiViz would be capable of visualizing any log containing vector clock
partial orderings given an improved log parser and log parsing options.
What is an example use case for this enhancement?
Logs that contain vector clocks generated without ShiVector could be visualized
with ShiViz.
Original issue reported on code.google.com by jenny.abrahamson on 6 Jun 2013 at 12:36
Original issue reported on code.google.com by
jenny.abrahamson
on 6 Jun 2013 at 12:36